Monthly
Authorization bypass in FileRise prior to 3.18.0 allows an authenticated, low-privileged user to read - and, when they also hold edit-own permission, modify - files they do not own by exploiting a collision in folder metadata filenames. FileRise flattens logical folder paths into metadata filenames by replacing '/', '\\' and spaces with hyphens, so distinct folders such as team/docs and team-docs resolve to the same <name>_metadata.json file; an attacker who controls one colliding folder and knows the target basename can overwrite the uploader-ownership metadata that read_own and ownership-restricted edit checks rely on, making a victim file appear attacker-owned. The issue is rated CVSS 7.1 (AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L) and is fixed in 3.18.0; exploitation requires a multi-user deployment, a crafted colliding folder name, pre-existing read_own access to the target folder and knowledge of the exact victim basename, and no public exploit identified at time of analysis. Single-tenant or single-user installations are effectively unaffected because no second user exists to victimize.
Sandbox escape in Google Chrome on macOS lets an attacker who has already compromised the renderer process execute arbitrary code outside the browser sandbox by delivering a crafted extension that abuses incorrect reference resolution in the Extensions subsystem, affecting all Mac builds prior to 155.0.8059.79. Google rates the issue High (Chromium severity: High) and has shipped a vendor fix, and there is no public exploit identified at time of analysis, with the CISA SSVC assessment recording exploitation as none. The impact is total once the chain fires (Scope:Changed, C:H/I:H/A:H), but high attack complexity (AC:H), required user interaction (UI:R) and the hard prerequisite of a prior renderer compromise make this a targeted second-stage escalation rather than a standalone remote exploit.
Duplicate-name tree entries pushed to Gitea ≤1.27.3 are stored and served inconsistently: the web diff and file views resolve such a path to the first entry, while `git checkout`, Gitea Actions and generated release archives resolve it to the last, so a contributor can open a pull request that looks benign to reviewers but runs or delivers attacker-controlled content at the same commit. Exploitation requires the ability to push a branch or open a pull request (contributor access, or a public instance allowing registration and fork-based PRs) and is only consequential where a consumer resolves the commit differently - CI auto-running on the PR, a developer checking it out, or a release tarball being built; there is no confirmed active exploitation and no public exploit code identified at time of analysis, with EPSS at 0.16% (4th percentile). Critically, upgrading fixes only new incoming objects - existing repositories are not rescanned, so a malicious tree already stored stays exploitable after the patch.
Arbitrary code execution outside the browser sandbox is possible in Google Chrome on macOS prior to 155.0.8059.39, where incorrect reference resolution in the WebAppInstalls component allows crafted network traffic to cross a process trust boundary. Exploitation is not standalone: the attacker must already have compromised the Chrome renderer process, which makes this a second-stage sandbox-escape primitive in a larger exploit chain rather than a directly reachable remote compromise, and the assessed vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H) reflects that non-trivial precondition. A vendor-released patch (Chrome 155.0.8059.39) is available, and no public exploit code was identified at the time of analysis.
Sandbox escape in Google Chrome on iOS (versions prior to 155.0.8059.39) allows a local attacker who has already compromised the renderer process to execute arbitrary code outside the browser sandbox via a local program. The flaw is an incorrect reference resolution (CWE-706) in the Passwords component, rated Medium by Chromium and carrying a CVSS 7.4 (AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H). No public exploit code or confirmed active exploitation has been identified at time of analysis; a vendor patch is available.
Incorrect reference resolution in Google Chrome on macOS before 155.0.8059.39 can disclose sensitive information to a remote attacker who uses social engineering to make the victim load a crafted HTML page. Exploitation requires a macOS user running an affected Chrome build who actively opens attacker-supplied content (UI:R), with no authentication required (PR:N) and network-delivered payloads (AV:N); there is no confirmed active exploitation and no public exploit code identified at time of analysis, and the only data supplied is a vendor patch and a Chromium issue. The signals conflict sharply: the headline CVSS of 8.8 (C:H/I:H/A:H) is not supported by the available evidence, and the assessed vector is confidentiality-only (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N, roughly 6.5 Medium), matching Chromium's own 'Medium' severity label, so real-world priority is lower than the 8.8 figure implies.
Google Chrome on Android releases before 155.0.8059.39 mishandle Autofill reference resolution, allowing a remote attacker who socially engineers a victim into opening a crafted HTML page to read sensitive information held in the browser's Autofill store. The CVSS vector PR:N means no authentication is needed, but the required user interaction (UI:R) and social-engineering dependency are the main practical barriers; no public exploit code has been identified at time of analysis. Our independent assessment scores this as confidentiality-only (CWE-706, use of incorrectly-resolved name or reference), so it should be treated as an information-disclosure issue rather than code execution or data tampering.
Google Chrome versions prior to 154.0.8037.57 contain an incorrectly-resolved name or reference flaw (CWE-706) that remote, unauthenticated attackers can trigger by convincing a user to load attacker-controlled web content; the issue is rated CVSS 3.1 8.3 High with scope change (S:C) and high confidentiality, integrity and availability impact. Exploitation is gated by mandatory user interaction (UI:R) and high attack complexity (AC:H), requiring non-trivial prerequisites such as specific timing, memory grooming or a race condition, and no public exploit code has been identified at time of analysis. Google has already shipped a stable-channel fix in Chrome 154.0.8037.57, so patched or auto-updated browsers are not exposed.
Local sandbox escape in Google Chrome on Windows (versions prior to 153.0.8010.52) lets an attacker who can already execute a program on the target host run arbitrary code outside the browser sandbox by abusing incorrect reference resolution in Chrome's Tracing component (CWE-706). The vendor rates it High with a CVSS of 8.1 (AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H), meaning exploitation is local-only, requires no user interaction, but is gated by high attack complexity - consistent with a race or timing-dependent condition that is not reliably repeatable. No public exploit code has been identified at time of analysis, and because a local foothold is a prerequisite, this is realistically a chained sandbox-escape stage rather than a standalone initial-access vulnerability.
Sandbox escape in vm2 before 3.11.7 allows an attacker who can already execute JavaScript inside the vm2 sandbox to bypass the external package allowlist and cause unauthorized host packages to be loaded and executed in the host context. The flaw is an incorrect authorization check: vm2 uses non-exact substring matching when validating package names against the allowlist, so a colliding package name that contains an allowlisted substring is approved. Exploitation requires the host application to use vm2 for untrusted code and to rely on the external package allowlist as a trust boundary; the CVSS vector indicates PR:L, meaning low privileges are required, and no public exploit or CISA KEV confirmed active exploitation was identified at time of analysis.
Authorization bypass in FileRise prior to 3.18.0 allows an authenticated, low-privileged user to read - and, when they also hold edit-own permission, modify - files they do not own by exploiting a collision in folder metadata filenames. FileRise flattens logical folder paths into metadata filenames by replacing '/', '\\' and spaces with hyphens, so distinct folders such as team/docs and team-docs resolve to the same <name>_metadata.json file; an attacker who controls one colliding folder and knows the target basename can overwrite the uploader-ownership metadata that read_own and ownership-restricted edit checks rely on, making a victim file appear attacker-owned. The issue is rated CVSS 7.1 (AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L) and is fixed in 3.18.0; exploitation requires a multi-user deployment, a crafted colliding folder name, pre-existing read_own access to the target folder and knowledge of the exact victim basename, and no public exploit identified at time of analysis. Single-tenant or single-user installations are effectively unaffected because no second user exists to victimize.
Sandbox escape in Google Chrome on macOS lets an attacker who has already compromised the renderer process execute arbitrary code outside the browser sandbox by delivering a crafted extension that abuses incorrect reference resolution in the Extensions subsystem, affecting all Mac builds prior to 155.0.8059.79. Google rates the issue High (Chromium severity: High) and has shipped a vendor fix, and there is no public exploit identified at time of analysis, with the CISA SSVC assessment recording exploitation as none. The impact is total once the chain fires (Scope:Changed, C:H/I:H/A:H), but high attack complexity (AC:H), required user interaction (UI:R) and the hard prerequisite of a prior renderer compromise make this a targeted second-stage escalation rather than a standalone remote exploit.
Duplicate-name tree entries pushed to Gitea ≤1.27.3 are stored and served inconsistently: the web diff and file views resolve such a path to the first entry, while `git checkout`, Gitea Actions and generated release archives resolve it to the last, so a contributor can open a pull request that looks benign to reviewers but runs or delivers attacker-controlled content at the same commit. Exploitation requires the ability to push a branch or open a pull request (contributor access, or a public instance allowing registration and fork-based PRs) and is only consequential where a consumer resolves the commit differently - CI auto-running on the PR, a developer checking it out, or a release tarball being built; there is no confirmed active exploitation and no public exploit code identified at time of analysis, with EPSS at 0.16% (4th percentile). Critically, upgrading fixes only new incoming objects - existing repositories are not rescanned, so a malicious tree already stored stays exploitable after the patch.
Arbitrary code execution outside the browser sandbox is possible in Google Chrome on macOS prior to 155.0.8059.39, where incorrect reference resolution in the WebAppInstalls component allows crafted network traffic to cross a process trust boundary. Exploitation is not standalone: the attacker must already have compromised the Chrome renderer process, which makes this a second-stage sandbox-escape primitive in a larger exploit chain rather than a directly reachable remote compromise, and the assessed vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H) reflects that non-trivial precondition. A vendor-released patch (Chrome 155.0.8059.39) is available, and no public exploit code was identified at the time of analysis.
Sandbox escape in Google Chrome on iOS (versions prior to 155.0.8059.39) allows a local attacker who has already compromised the renderer process to execute arbitrary code outside the browser sandbox via a local program. The flaw is an incorrect reference resolution (CWE-706) in the Passwords component, rated Medium by Chromium and carrying a CVSS 7.4 (AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H). No public exploit code or confirmed active exploitation has been identified at time of analysis; a vendor patch is available.
Incorrect reference resolution in Google Chrome on macOS before 155.0.8059.39 can disclose sensitive information to a remote attacker who uses social engineering to make the victim load a crafted HTML page. Exploitation requires a macOS user running an affected Chrome build who actively opens attacker-supplied content (UI:R), with no authentication required (PR:N) and network-delivered payloads (AV:N); there is no confirmed active exploitation and no public exploit code identified at time of analysis, and the only data supplied is a vendor patch and a Chromium issue. The signals conflict sharply: the headline CVSS of 8.8 (C:H/I:H/A:H) is not supported by the available evidence, and the assessed vector is confidentiality-only (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N, roughly 6.5 Medium), matching Chromium's own 'Medium' severity label, so real-world priority is lower than the 8.8 figure implies.
Google Chrome on Android releases before 155.0.8059.39 mishandle Autofill reference resolution, allowing a remote attacker who socially engineers a victim into opening a crafted HTML page to read sensitive information held in the browser's Autofill store. The CVSS vector PR:N means no authentication is needed, but the required user interaction (UI:R) and social-engineering dependency are the main practical barriers; no public exploit code has been identified at time of analysis. Our independent assessment scores this as confidentiality-only (CWE-706, use of incorrectly-resolved name or reference), so it should be treated as an information-disclosure issue rather than code execution or data tampering.
Google Chrome versions prior to 154.0.8037.57 contain an incorrectly-resolved name or reference flaw (CWE-706) that remote, unauthenticated attackers can trigger by convincing a user to load attacker-controlled web content; the issue is rated CVSS 3.1 8.3 High with scope change (S:C) and high confidentiality, integrity and availability impact. Exploitation is gated by mandatory user interaction (UI:R) and high attack complexity (AC:H), requiring non-trivial prerequisites such as specific timing, memory grooming or a race condition, and no public exploit code has been identified at time of analysis. Google has already shipped a stable-channel fix in Chrome 154.0.8037.57, so patched or auto-updated browsers are not exposed.
Local sandbox escape in Google Chrome on Windows (versions prior to 153.0.8010.52) lets an attacker who can already execute a program on the target host run arbitrary code outside the browser sandbox by abusing incorrect reference resolution in Chrome's Tracing component (CWE-706). The vendor rates it High with a CVSS of 8.1 (AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H), meaning exploitation is local-only, requires no user interaction, but is gated by high attack complexity - consistent with a race or timing-dependent condition that is not reliably repeatable. No public exploit code has been identified at time of analysis, and because a local foothold is a prerequisite, this is realistically a chained sandbox-escape stage rather than a standalone initial-access vulnerability.
Sandbox escape in vm2 before 3.11.7 allows an attacker who can already execute JavaScript inside the vm2 sandbox to bypass the external package allowlist and cause unauthorized host packages to be loaded and executed in the host context. The flaw is an incorrect authorization check: vm2 uses non-exact substring matching when validating package names against the allowlist, so a colliding package name that contains an allowlisted substring is approved. Exploitation requires the host application to use vm2 for untrusted code and to rely on the external package allowlist as a trust boundary; the CVSS vector indicates PR:L, meaning low privileges are required, and no public exploit or CISA KEV confirmed active exploitation was identified at time of analysis.