Suse
Monthly
Missing authorization enforcement in Google Chrome builds earlier than 154.0.8037.57 (classified CWE-862 and tagged as an authentication bypass) lets an attacker defeat an access-control decision in the browser, with the impact scored as high confidentiality and high integrity loss (CVSS 3.1 base 8.1, AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N). The flaw is network-delivered and requires no authentication or prior privileges, but exploitation is not silent: the victim must navigate to or render attacker-controlled web content (UI:R), which keeps the practical attack path dependent on user browsing behavior rather than on a remotely reachable service. Google has shipped the fix in Chrome 154.0.8037.57 and the issue is tracked as ENISA EUVD-2026-89222 / Chromium issue 540265100; no public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV, so there is no confirmed active exploitation.
An out-of-bounds memory write in Google Chrome allows an unauthenticated, remote attacker to corrupt memory and potentially execute arbitrary code or crash the browser when a victim opens a crafted web page, as reflected by the CVSS 3.1 vector AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H (9.6, scope-changed). The flaw is classified as CWE-787 (out-of-bounds write) and is addressed by the vendor's stable channel update for desktop, with the fix credits originating from the Ubuntu vendor reporting channel, meaning downstream Chromium packages are also in scope. At time of analysis there is no public exploit identified, no CISA KEV listing, and no EPSS data provided; however, because browser memory-corruption bugs of this class are historically attractive to exploit developers, this remains a high-priority patching item despite the absence of exploitation telemetry.
The affected product and the nature of the security impact for CVE-2026-95325 cannot be established from the intelligence available at time of analysis. The only signal present is that the entry was reported by the vendor source 'ubuntu', with no description, CVSS score or vector, CWE mapping, CPE identifiers, references, EPSS score, or KEV status supplied; the independent assessment accordingly classifies this as a data-void entry with no analyzable signals. No public exploit identified at time of analysis, and there is no basis to characterize the attack vector, authentication requirements, or affected versions.
Ubuntu Linux is the only product attributable to CVE-2026-95319, and the sole intelligence signal available is a vendor:ubuntu report with no accompanying advisory text, version range, or affected component. No description, CVSS score, CVSS vector, CWE classification, CPE string, EPSS score, KEV status, or reference link was supplied, so the vulnerability class, attack vector, privilege requirements, and impact cannot be characterized. No public exploit code has been identified at time of analysis, but this reflects absent data rather than a confirmed absence of exploitation, and the entry must be treated as unassessable until the upstream NVD or Ubuntu security advisory is retrieved.
Cross-site request forgery in Google Chrome on desktop lets a remote, unauthenticated attacker achieve high confidentiality, integrity and availability impact against a victim who is persuaded to visit or interact with an attacker-controlled page (CVSS 3.1 vector AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 8.8). Only Chrome installations older than 154.0.8037.57 are affected, and Google has shipped a stable channel fix in that build, with the issue tracked upstream as Chromium issue 511791538 and Ubuntu listed among the reporters. No public exploit code has been identified and the flaw is not in CISA KEV, but note that the official description is empty and the CWE-352 label is hard to reconcile with the full C/I/A impact claimed, so the exact triggering feature remains unconfirmed.
Race condition in Google Chrome's stable channel allows a remote, unauthenticated attacker who persuades a user to interact with crafted content to win a time-of-check/time-of-use window and affect data beyond the vulnerable component's security scope. The CVSS 3.1 base score of 8.0 (AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N) reflects high confidentiality and integrity impact with no availability impact, tempered by high attack complexity; no public exploit code or CISA KEV entry was identified at time of analysis. The flaw is addressed in the 154.0.8037.57 stable channel update, and while the vendor feed tags it Information Disclosure, the scoring indicates a broader boundary-crossing defect, so this is best treated as a moderately high-priority browser issue with partly inferred impact.
Improper input validation in Google Chrome before 154.0.8037.57 allows unauthenticated remote attackers to achieve high confidentiality, integrity, and availability impact with a scope change, though exploitation requires the victim to visit attacker-controlled web content and overcome high attack complexity. The flaw, tracked as CVE-2026-95341 with a CVSS 8.3 base score, affects default installations of Chrome on all platforms and could permit renderer-level code execution or sandbox escape; no public exploit identified at time of analysis. Vendor-released patch 154.0.8037.57 addresses the issue.
Use-after-free memory corruption in Google Chrome allows remote attackers to corrupt memory and potentially execute code beyond the browser's normal security boundaries when a victim loads attacker-controlled web content. The flaw carries a CVSS 9.6 with vector AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H, meaning no authentication is required, the attack is network-delivered, and the scope change plus full confidentiality, integrity, and availability impact indicate a flaw that can affect resources beyond the vulnerable component - consistent with a renderer sandbox escape. Exploitation requires the victim to visit a malicious page or render a malicious embedded resource such as an ad or iframe; at time of analysis there is no public exploit identified, but the vendor has released a patched stable-channel build and defenders should treat untrusted browsing on unpatched Chrome as high risk.
Type confusion in Google Chrome's core rendering code allows remote attackers to corrupt memory and execute arbitrary code inside the browser renderer, affecting Chrome builds prior to 154.0.8037.57 on all platforms. Exploitation requires the victim to load attacker-controlled web content (a malicious or compromised page), matching the CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H profile - no credentials are needed, and default configurations are exposed because the flaw sits in normal rendering rather than an optional feature. At the time of analysis there is no CISA KEV listing and no public exploit identified at time of analysis; the impact is contained to the sandboxed renderer (S:U), so full host compromise would require a separate sandbox escape not described in this record, but the integrity and confidentiality impact within the renderer is high and the issue is rated 8.8.
Type confusion in Google Chrome's renderer allows remote attackers to corrupt memory and potentially achieve code execution inside the browser by convincing a victim to open a crafted web page; the attack is network-delivered, requires no authentication (PR:N), and has low complexity, with the only meaningful barrier being that the user must interact with attacker-controlled content (UI:R). A vendor patch is available per the September 2026 stable-channel update, and no public exploit code or confirmed active exploitation was identified at time of analysis, so the high priority here is driven mainly by Chrome's ubiquity rather than observed attacks. Because the CVSS scope is unchanged (S:U), full-system compromise as scored would likely require chaining this bug with a separate sandbox-escape vulnerability, while on its own the flaw is expected to yield renderer-level memory corruption, information disclosure, and potential arbitrary code within the sandboxed process.
Risk cannot be meaningfully assessed from the supplied data: CVE-2026-95283 is recorded only as a vendor-reported entry from Ubuntu, with the description marked '[Unknown description]' and no CVSS score, CVSS vector, CWE, CPE, or affected source package provided. Because the impacted component, deployment mode, and attack surface are all unidentified, no statement can be made about what an attacker could achieve, which versions are affected, or what preconditions (authentication, user interaction, configuration) would be required. There is no KEV listing and no public exploit code identified at time of analysis, so the entry should be treated as an unassessed tracking record rather than a confirmed exploitable issue.
Heap-based buffer overflow in Google Chrome desktop (stable channel) allows a remote, unauthenticated attacker to corrupt heap memory when a victim renders attacker-controlled web content such as a malicious page, iframe, or ad, yielding high impact to confidentiality, integrity, and availability with a changed scope that suggests effects can extend beyond the initially affected component. Exploitation requires user interaction (UI:R) - the victim must load the hostile content - but needs no credentials (PR:N), is network-reachable (AV:N) and low complexity (AC:L), making actively browsing, unpatched endpoints the realistic exposure. No public exploit has been identified at time of analysis; the referenced Chrome stable channel advisory and Chromium issue 551573368 confirm a vendor fix, and the independent assessment rates this a genuine high priority at CVSS 9.6.
Risk cannot be meaningfully assessed from the available data. CVE-2026-95281 is tracked in the Ubuntu security database, which establishes only that it affects software shipped as a package within the Ubuntu distribution; the upstream project, the vulnerable component, and the affected Ubuntu releases are all unspecified. No description, CVSS vector, CWE, CPE, KEV status, or exploit data was provided, and no public exploit has been identified at time of analysis, so the attack vector, privilege requirements, and user-interaction prerequisites remain unknown and must be sourced from the corresponding Ubuntu Security Notice or the NVD entry.
No technical details are available for CVE-2026-95338: the description field is empty and no CVSS score, CVSS vector, CWE classification, CPE string, or affected package name was supplied alongside the record. The only identifying signal is that the issue was reported under the vendor:ubuntu source, indicating it is tracked as a vulnerability in a package distributed through Ubuntu's repositories and handled via the Ubuntu Security Notice process. Risk cannot be meaningfully assessed from the available data, and there is no public exploit identified at time of analysis; exploitation prerequisites, impact, and affected versions must be obtained from the Ubuntu Security Notice for this CVE before any triage decision is made.
A missing-authorization flaw (CWE-862) in Google Chrome desktop builds prior to 154.0.8037.57 can be triggered by an unauthenticated local attacker with no user interaction, and the assessed CVSS vector (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 8.4) rates confidentiality, integrity and availability impact as high, consistent with the 'Authentication Bypass' tagging applied by the reporting vendor. The local attack vector and absence of a user-interaction requirement mean the attacker must already have some form of local execution context on the target host, which sharply constrains mass remote exploitation; no public exploit code has been identified at time of analysis and EPSS is low at 0.24% (13th percentile). Exploitation is limited to unpatched builds and is fully mitigated by the vendor-released fix in Chrome 154.0.8037.57, so this should be handled as a moderate-priority patch rather than an emergency, though the 8.4 score and high CIA impact still warrant prompt update cycles.
Ubuntu Linux is the only product implicated by the available reporting for CVE-2026-95311, a record attributed to the Ubuntu vendor security team, but the vulnerability description is unpublished and no CVSS score or vector, CWE classification, CPE identifier, EPSS estimate, or CISA KEV entry accompanies it, so the affected component, version range, and attack vector cannot be stated. No public exploit code has been identified at time of analysis, and there is no evidence of confirmed active exploitation. Risk cannot be meaningfully assessed from the provided data; the only actionable intelligence is the vendor attribution, which indicates Canonical is coordinating the record and that the Ubuntu Security Notices feed and the upstream advisory should be monitored for the eventual disclosure.
Use-after-free memory corruption in Google Chrome desktop builds prior to 154.0.8037.57 allows a remote, unauthenticated attacker to trigger heap memory corruption in the browser by convincing a victim to load attacker-controlled web content - a single page navigation is sufficient (UI:R, PR:N, AV:N). The flaw is rated CVSS 9.6 with a scope change (S:C), indicating the corruption can affect resources beyond the initially vulnerable component; no authentication, prior privileges, or non-default configuration is required, though exploitation hinges entirely on user interaction with a malicious or compromised page. Google has already shipped a fixed build (154.0.8037.57) on the stable channel, and no public exploit code or confirmed active exploitation was identified at time of analysis, making this a genuine high-priority patch-and-update item rather than an emergency zero-day response.
Use-after-free memory corruption in Google Chrome builds prior to 154.0.8037.57 allows a remote, unauthenticated attacker to corrupt memory and potentially execute code within the browser renderer by persuading a victim to load attacker-controlled web content (CVSS 3.1 base 8.8, AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). No public exploit code has been identified at time of analysis and the flaw is not listed in CISA KEV. Exploitation requires the victim to open a malicious page or attacker-embedded content in a trusted site, and because the assessed scope is unchanged (S:U) the impact is initially confined to the renderer sandbox, so full host takeover would require a separate sandbox escape; Google has shipped a fixed build that is distributed through Chrome auto-update, shrinking the exposure window on kept-current fleets.
Use-after-free memory corruption in Google Chrome's desktop stable channel lets remote, unauthenticated attackers achieve high-integrity/high-availability impact against a victim who simply renders attacker-controlled web content - the attacker must first convince the user to visit a malicious or compromised page (or load a malicious ad/iframe), which is why the assessed vector carries UI:R despite PR:N. Per our independent assessment, a practical exploit must win a heap-grooming race to reclaim the freed object and, because of the scope change (S:C), chain a further sandbox escape to fully realize the 9.6 severity, so exploitation is possible but not trivial. A vendor fix is available in the referenced Chrome stable channel update, and no public exploit code has been identified at time of analysis; the specific vulnerable component and exact fixed build are not disclosed in the available data.
Heap-based buffer overflow in Google Chrome builds earlier than 154.0.8037.57 allows unauthenticated remote attackers to corrupt memory when a victim loads attacker-controlled web content, with a CVSS base score of 9.6 (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H) reflecting scope change and potential high confidentiality, integrity, and availability impact. Exploitation requires user interaction - visiting a malicious site, a compromised page, or a malicious ad - and full host compromise would most likely require chaining this renderer-process overflow with a separate sandbox-escape bug rather than this flaw alone. Risk signals conflict in the usual browser-bug pattern: EPSS is only 0.29% (19th percentile), there is no CISA KEV listing, and no public exploit identified at time of analysis, while Chrome's silent auto-update rapidly shrinks the vulnerable population and a vendor patch is already available.
Memory corruption via use-after-free in Google Chrome allows remote code execution or sensitive data disclosure in the renderer when a victim loads attacker-controlled web content in any version earlier than 154.0.8037.57. The flaw is network-reachable, low-complexity and requires no authentication (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 8.8 High), but it does require the user to open a malicious page, ad or iframe, and because the scope is Unchanged the immediate impact stays inside the sandboxed renderer, so full host compromise realistically needs a second, chained sandbox-escape bug. There is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV); a vendor patch is available in Chrome 154.0.8037.57.
An authorization-bypass flaw in Google Chrome desktop builds prior to 154.0.8037.57 lets remote attackers escape a security boundary by having the victim load crafted web content in the browser. Successful exploitation crosses a sandbox boundary (S:C) and can compromise confidentiality, integrity and availability of the affected system, but the CVSS vector (AC:H, UI:R) means the attacker must satisfy specific timing or memory-state conditions and the user must actively visit or interact with the malicious page. No confirmed active exploitation (not in CISA KEV), no public exploit code identified at time of analysis, and a vendor patch is available, so prioritization should reflect a high-severity but hard-to-trigger client-side issue rather than an imminent mass-exploitation event.
Information disclosure in Google Chrome desktop builds earlier than 154.0.8037.57 lets an attacker who shares a local network segment with the victim trigger a flaw that the assessed CVSS scores as high impact across confidentiality, integrity, and availability (CVSS 8.0, AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). The attacker needs no authentication or elevated privileges (PR:N), but must be positioned on the same adjacent L2 segment as the target (AV:A) and must get the victim to load attacker-influenced content (UI:R) - a combination that substantially constrains mass or opportunistic exploitation. An official fix is already available on the stable channel and no public exploit code has been identified at time of analysis, so risk here is driven primarily by Chrome's ubiquity and by unpatched client exposure rather than by observed exploitation activity.
CVE-2026-95277 is currently an effectively empty record: no description, CVSS score, CVSS vector, CWE mapping, affected product, version range, or CPE data has been published, and the only intelligence signal is attribution to the Ubuntu vendor reporting channel. Because the vulnerability class, attack vector, authentication requirements, and impacted component are all unknown, risk cannot be meaningfully assessed from the available data and no exploit status can be confirmed - there is no public exploit identified at time of analysis, and the entry is not listed as confirmed actively exploited (CISA KEV). Organizations should treat this identifier as a placeholder to be re-triaged once Ubuntu publishes a corresponding security notice (USN) or the upstream CVE record is populated.
Out-of-bounds memory write in Google Chrome (desktop builds) lets remote, unauthenticated attackers corrupt browser memory when a victim loads attacker-controlled web content. The vendor CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:R/S:U with C:H/I:H/A:H (base 8.8), so the only prerequisite is that a user navigates to or renders a malicious page, and because the vector is scope-unchanged the memory corruption is expected to remain within the renderer/browser process rather than granting an inherent sandbox escape. The underlying flaw is an out-of-bounds write (CWE-787) in Chrome builds predating the vendor's September 2026 stable channel fix; patched builds are not affected, and no public exploit code or confirmed active exploitation was identified at time of analysis.
Use-after-free memory corruption in Google Chrome desktop builds earlier than 154.0.8037.57 (CWE-416) allows remote attackers to corrupt memory and potentially achieve code execution inside the renderer process when a victim opens a malicious or compromised web page. The flaw is remotely reachable with low attack complexity and no privileges required (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, 8.8), but it hinges on user interaction and, because scope is unchanged, exploitation is contained to the sandboxed renderer; full host compromise realistically requires chaining a separate sandbox-escape bug. There is no confirmed active exploitation and no public exploit identified at time of analysis, so the elevated priority is driven by Chrome's ubiquity and the reliability of memory-safety bugs in this class rather than by observed attacks; vendor patches are already available.
Google Chrome stable builds earlier than 154.0.8037.57 contain a race condition (CWE-362) that a remote attacker can trigger by getting a victim to load attacker-controlled web content, yielding high confidentiality, integrity, and availability impact within the browser's renderer sandbox. No authentication or special browser configuration is required (CVSS 8.8, AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), though user interaction - visiting or rendering hostile content - is the primary exploitation prerequisite, and a separate sandbox escape would be needed to reach the host. Exploitation status: no public exploit identified at time of analysis, and there is no CISA KEV listing; the vendor has shipped a fixed release.
Google Chrome desktop builds earlier than 154.0.8037.57 are affected by an improper input validation flaw (CWE-20) rated CVSS 8.3 (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H), in which an unauthenticated remote attacker who persuades a user to load attacker-controlled web content can potentially achieve high confidentiality, integrity and availability impact that crosses a browser security boundary. Although the public tagging labels this issue as information disclosure, the assessed vector indicates broader high impact across all three CIA dimensions combined with a scope change (S:C), consistent with escaping the Chrome renderer sandbox. Exploitation is constrained by mandatory user interaction and high attack complexity, no public exploit has been identified at time of analysis, and Google has already shipped the fix in the stable channel, so auto-updating installations are remediated on restart.
Risk cannot be meaningfully assessed for CVE-2026-95299 because the vulnerability record contains no description, no CVSS score or vector, no CWE mapping, and no CPE/product identifiers; the only attributable data point is that the issue was reported by the vendor Ubuntu. Consequently the affected component, the attack surface, and any prerequisite conditions remain unknown, and no public exploit has been identified at time of analysis. Analysts should treat this identifier as unresolved rather than low-risk: an empty record frequently reflects a placeholder or embargoed entry that is populated later, so the absence of detail is not evidence of low severity.
Improper input validation in Google Chrome before 154.0.8037.57 can be triggered when a victim loads attacker-controlled web content, yielding a scope-changed impact rated high for confidentiality, integrity, and availability (CVSS 8.3). Exploitation is network-reachable without credentials (PR:N) but demands victim interaction (UI:R) plus non-trivial preconditions such as specific memory state, heap grooming, or timing windows (AC:H), and the affected component is undisclosed because chromium issue 517730821 is access-restricted. No public exploit code and no confirmed active exploitation were identified at time of analysis; a vendor patch is available in the Chrome stable channel at 154.0.8037.57.
A use-after-free in Google Chrome desktop can be triggered when a victim renders attacker-controlled web content, allowing memory corruption that may lead to code execution or disclosure of sensitive in-process data. Affected are Chrome desktop builds on Windows, macOS, and Linux prior to the September 2026 stable channel update; the CVSS vector (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H, 9.6) requires no authentication or privileges but does require the victim to open or load a malicious or compromised page, and the S:C metric indicates the attack can affect a component beyond the one that is corrupted. Vendor-released patch available; no public exploit identified at time of analysis, and the reporting originator is Ubuntu.
Use-after-free memory corruption in Google Chrome builds earlier than 154.0.8037.57 allows a remote, unauthenticated attacker to corrupt memory in the browser by having a victim load attacker-controlled web content, yielding code execution with high confidentiality, integrity, and availability impact (CVSS 3.1 base 8.8, CWE-416). Exploitation is network-reachable with low complexity and requires no credentials, but is gated on user interaction (UI:R) - the victim must visit a malicious page or view attacker-controlled content such as a malicious ad or iframe. Because scope is unchanged (S:U), the primitive is contained within the renderer process, so full host compromise realistically requires chaining an additional sandbox-escape vulnerability; a fixed build is already available and there is no public exploit identified at time of analysis (no CISA KEV listing, no confirmed in-the-wild activity reported in the supplied intelligence).
Google Chrome on the desktop stable channel carries a vendor-patched security defect tracked as CVE-2026-95347, disclosed through Google's Chrome Releases stable-channel update in September 2026. The actual impact is currently undetermined: no description, CVSS score or vector, CWE classification, or affected version range has been published, so the vulnerability class, whether attackers must be authenticated, and whether user interaction (such as visiting a crafted page) is required cannot be confirmed from available data. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and no EPSS probability or SSVC decision data exists to refine the risk; this should be treated as a patch-priority item pending the details in the vendor advisory.
Use-after-free memory corruption in Google Chrome before 154.0.8037.57 allows a remote, unauthenticated attacker to potentially escape the browser's renderer sandbox by persuading a victim to visit attacker-controlled web content. Exploitation requires mandatory user interaction (UI:R) and a high-complexity precondition such as precise heap grooming or a timing race (AC:H), and no public exploit has been identified at time of analysis. Google has issued a vendor-released patch in version 154.0.8037.57 that removes the vulnerable code path.
Heap-based buffer overflow (CWE-122) in Google Chrome's stable channel, addressed in the September 2026 desktop stable-channel update, lets remote, unauthenticated attackers corrupt heap memory in a vulnerable build and potentially escape the browser's renderer sandbox for full confidentiality, integrity, and availability impact (CVSS 3.1 base 9.6, S:C). Exploitation requires the victim to interact with attacker-controlled web content - typically visiting a malicious page or rendering a hostile ad - so the practical window depends on how quickly users and Linux distributions apply the update. No public exploit identified at time of analysis, and the issue is not listed in CISA KEV; details remain limited because the referenced Chromium issue tracker entry is access-restricted.
Use-after-free in Google Chrome builds prior to 154.0.8037.57 allows remote, unauthenticated attackers to corrupt memory when a victim loads attacker-controlled web content, with potential for information disclosure and code execution. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 8.8) indicates low-complexity, network-reachable exploitation that is gated only by user interaction, and because scope is unchanged (S:U) any initial code execution is confined to the renderer sandbox, so full host compromise would require chaining a separate sandbox escape. No public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis, and a vendor patch in Chrome 154.0.8037.57 is available.
Type confusion in Google Chrome builds prior to 154.0.8037.57 lets a remote attacker who convinces a victim to load attacker-controlled web content corrupt memory inside the renderer and potentially achieve code execution in that process. The flaw is rated CVSS 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, CWE-843), meaning no authentication or privileges are required but exploitation is not zero-click: the victim must render a malicious page, and because scope is unchanged the initial compromise is confined to the renderer sandbox unless chained with a separate sandbox escape. No public exploit code has been identified at time of analysis and the issue is not listed as confirmed actively exploited (CISA KEV); a vendor-released patch is available in Chrome 154.0.8037.57.
Use-after-free memory corruption in Google Chrome desktop builds prior to 154.0.8037.57 allows remote attackers to achieve high-integrity and high-confidentiality impact against a victim who loads attacker-controlled web content and performs some interaction with it, but exploitation is not trivially repeatable: with AC:H it depends on winning a race or reliably grooming heap layout rather than a single deterministic trigger. The flaw is reachable without authentication (PR:N) and the vector's scope change (S:C) indicates the assessed impact crosses a component boundary, yet no public exploit code has been identified at time of analysis and there is no CISA KEV listing, so this should be treated as a high-priority patching item rather than a confirmed in-the-wild threat. A vendor patch is available.
Authentication bypass in Google Chrome prior to 154.0.8037.57 allows an attacker with local access to the machine to slip past an authorization check in a browser component, yielding high confidentiality, integrity, and availability impact. The assessed CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:N) means no privileges and no user interaction are needed once local access exists, so the realistic prerequisite is the ability to execute or otherwise interact with the vulnerable Chrome component on the host rather than reaching it over the network; a purely remote, unauthenticated web-based attack is not supported by the available data. Exploitation signals are currently weak and non-urgent: EPSS is only 0.22% (12th percentile), there is no CISA KEV listing, and no public exploit code was identified at time of analysis, while the vendor has shipped a fixed build. Note that the affected feature or component is not named in the available data because no vendor description was published, so the exact local precondition should be confirmed against the Chrome release advisory.
Timing-based leakage of the single recovery token in OpenBao lets a remote, unauthenticated attacker who can reach the instance while it is running in highly privileged recovery mode recover that token and then read or modify data on the OpenBao instance. The exposure is constrained to the transient recovery-mode break-glass state rather than the normal serving configuration, and exploitation requires collecting a large volume of low-noise timing samples against the recovery endpoint (reflected in the CVSS 4.0 rating of 9.2 with AC:H and AT:P, and in the assessed CVSS 3.1 vector AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H). The vendor addressed the flaw in OpenBao v2.6.0; no public exploit identified at time of analysis.
Arbitrary code execution in GNU Emacs 28.1 through 31.1 is triggered simply by opening a crafted file: an untrusted read-symbol-shorthands value supplied by that file reaches the Lisp reader's intern and unintern functions and is honored under Emacs's default configuration, so no special user settings or opt-ins are required. Exploitation is bounded by delivery - the attacker must get a victim to open the malicious file locally (AV:L with UI:R), and any resulting code executes with the privileges of the user running Emacs; no network service, listener, or authentication is involved. The issue carries a CVSS 4.0 score of 7.5 and is assessed under CVSS 3.1 as AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, with high confidentiality, integrity, and availability impact and no public exploit identified at time of analysis.
Local cross-user code execution with privilege-escalation potential affects the Windows builds of GNU wget distributed by eternallybored.org (releases 0 through 1.21.4 inclusive). The flaw is a hardcoded configuration location, C:\msys64, that unprivileged users can write to: a low-privileged local attacker who plants a wgetrc there can abuse the use_askpass directive so that arbitrary code is executed in the security context of a higher-privileged user who later runs the affected wget build. The attack is not remotely reachable and does not trigger on its own, which is captured by the UI:R component of the CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 7.8), and no public exploit code was identified at time of analysis.
Local privilege escalation to root in Netdata versions prior to 2.10.4: the setuid-root ndsudo helper command fail2ban-client-status-socket accepted a caller-supplied --socket_path argument from the low-privileged netdata service account, letting that account point root's fail2ban-client at an attacker-controlled UNIX socket. Because fail2ban-client's CSocket.receive() deserializes the socket response with pickle.loads(), a crafted reply yields attacker-controlled code execution as root on any host where fail2ban-client is installed and the setuid ndsudo helper is present (default in affected packaged builds). The vector is strictly local (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H), so a prior foothold as the netdata account is mandatory, and hosts without fail2ban-client are not exploitable through this path; no public exploit code has been identified at time of analysis.
Memory exhaustion in Netdata versions prior to 2.11.0 allows a remote, unauthenticated attacker to inflate small, highly compressed WebSocket frames into large server-side allocations and, by repeating this across concurrent connections, drive the monitoring process to memory exhaustion and termination. The weakness sits in the unauthenticated WebSocket server's permessage-deflate handling, which is negotiated before authentication, so exploitation requires only network reachability to the default web listener (0.0.0.0:19999) - instances bound to localhost or shielded by firewalls are not reachable. Vendor-released patch: 2.11.0, which introduces a compressed-to-decompressed ratio cap; no public exploit code identified at time of analysis and no CISA KEV entry, but the independent assessment rates this a legitimate availability risk given the trivial trigger and the CVSS 3.1 score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).
Remote, unauthenticated denial of service against applications running FasterXML jackson-core 2.17.0 through 2.18.10: a JSON string of attacker-supplied numeric-looking text coerced into a BigDecimal, BigInteger, Double, or Float target drives NumberInput.looksLikeValidNumber() into quadratic regular-expression backtracking, and a single 160,000-character value was measured at roughly 74 seconds, so a small number of concurrent requests of ordinary body size can exhaust a server's request-handling thread pool. Reachability is narrowed by the data-binding requirement: only endpoints where jackson-databind's StdDeserializer/NumberDeserializers perform String-to-number coercion are exposed, and 2.16.x and earlier do not contain the affected method at all. No public exploit code identified at time of analysis, and no CISA KEV confirmation of active exploitation.
Unauthenticated remote code execution in SGLang 0.5.11 through 0.5.14 occurs when the multimodal generation runtime is launched in disaggregated-diffusion mode, where the DiffusionServer orchestrator binds a ZeroMQ ROUTER socket to a network-reachable interface with no authentication and passes the final frame of every received multipart message directly into pickle.loads() before any validation is performed. Rated CVSS 3.1 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), the flaw lets any remote party that can deliver a multipart ZMQ message to that socket execute arbitrary Python code in the serving process, yielding full compromise of confidentiality, integrity and availability on the host. No public exploit identified at time of analysis; exploitation requires the exposed orchestrator socket to be reachable beyond localhost, so loopback-bound or single-node deployments are not remotely exploitable.
Integer overflow in libstdc++ within Red Hat Hardened Images can cause undersized memory allocations, leading to memory corruption or application instability when a consuming application passes an attacker-controllable large size to the C++ new or new[] operator. Exploitation requires a specific application input path that triggers CWE-190 and an exploitable heap layout, as reflected in the High severity (CVSS 7.7, AC:H) assigned by Red Hat; the flaw is not exploitable against libstdc++ in isolation. No public exploit code, proof-of-concept, or CISA KEV listing is identified in the available data.
Denial of service in Erlang/OTP's ASN.1 OBJECT IDENTIFIER decoders allows a remote, unauthenticated attacker to stall TLS-processing services by sending a crafted certificate during the handshake. Erlang/OTP releases from OTP 17.0 up to the fixed versions OTP 27.3.4.18, OTP 28.5.0.7 and OTP 29.1.1 are affected whenever the service parses a peer's X.509 certificate - the default for TLS clients (which always parse the server certificate) and for mutual-TLS servers - because the vulnerable BER OID decoder runs before signature and trust-chain verification, so an untrusted self-signed certificate is sufficient to trigger it. A single crafted OID with one very large arc (roughly 262 KB of continuation bytes) burns about 13 seconds of CPU, so sustained denial of service requires repeated connections; no public exploit code identified at time of analysis, and the impact is availability only (vendor CVSS 8.2; independently assessed as CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).
Authenticated remote attackers can exhaust node memory on Erlang/OTP SSH daemons by repeatedly opening "session" channels that never receive a shell, exec, or subsystem handler, eventually driving the BEAM emulator out of memory and terminating it - which kills every application sharing that node, not just the SSH service. The flaw (CWE-770) affects OTP 17.0 through 27.3.4.18, 28.5.0.7, and 29.1.1 (ssh 3.0.1 through 5.2.11.13, 5.5.2.6, and 6.0.6); an attacker must be able to complete SSH authentication first, but no user interaction, special configuration, or valid file/credential access is required, and CVSS scores it 7.1 (CVSS 4.0 availability-high, PR:L). No public exploit identified at time of analysis, and vendor-released patches are available. The documented max_channels daemon option does not mitigate the attack, so operators cannot rely on it as a stopgap.
Erlang/OTP's ssl application in affected releases (OTP 22.2 through the fixed 27.3.4.18, 28.5.0.7 and 29.1.1) will complete a TLS 1.3 client handshake against any peer that answers with an unsolicited pre_shared_key extension, allowing that peer to impersonate the intended server while holding no certificate, no private key and no prior session. Because the bogus resumption flag short-circuits certificate handling, ssl:connect returns {ok, Socket} even though certificate path validation, verify_fun, hostname verification, partial_chain, CRL checking and OCSP stapling are all skipped; an unauthenticated network-positioned attacker (man-in-the-middle, hijacked route/DNS, or a server the client is lured into contacting) can exploit this, and clients restricted to TLS 1.2 are not affected. A vendor patch is available and no public exploit code has been identified at time of analysis.
Heap-based buffer overflow in libslirp's DHCPv6 and TFTP reply builders lets a malicious guest write attacker-controlled content and length past the end of the host-side reply buffer, causing host process crashes (denial of service) and potentially arbitrary code execution in the host. The flaw only manifests when the host interface is configured with a small, non-default MTU - the default MTU is explicitly unaffected - and requires the guest to reach libslirp's built-in DHCPv6 or TFTP service, which makes this a guest-to-host escape surface for QEMU user networking and slirp4netns rootless containers. Red Hat Enterprise Linux 8, 9 and 10 and OpenShift Container Platform 4 ship affected builds; no public exploit code and no confirmed active exploitation were identified at time of analysis, and the assessed vector is unauthenticated (PR:N) but high complexity (AC:H) because of the configuration prerequisite.
Unauthenticated path traversal in the Dancer2 Perl web framework (versions 2.1.0 up to but not including 2.2.0) lets a remote attacker read arbitrary files that the worker process can access, including configuration files such as config.yml stored above public_dir. The flaw only manifests in a non-default deployment where the application names File in its route_handlers configuration and sets static_handler to 0 - because the default static handler refuses dot segments before the File route executes; applications left at defaults are not affected. The vendor has released Dancer2 2.2.0 with a containment fix, EPSS is low (0.19%, 8th percentile), and no public exploit code or confirmed active exploitation was identified at time of analysis.
Security-control bypass in the Dancer2 Perl web framework (2.0.0 through 2.1.x) lets a refused route execute anyway: when an application enforces an authorization or security check by having a 'before' hook die and also registers an on_hook_exception handler that halts the response, the post-exception cleanup still runs and destroys the request, response and session the dispatcher needs, so the route body the hook meant to refuse runs and its writes land. The flaw requires that specific non-default application design - apps that do not refuse via dying hooks, or whose exception handler does not halt the response, are not affected - and, when the pattern is present, a single unauthenticated remote request is enough to trigger it (AV:N/AC:L/PR:N/UI:N), giving a high integrity impact on denial-protected state changes. EPSS is 0.17% (7th percentile) and there is no public exploit identified at time of analysis; CISA's SSVC rates exploitation as none, automatable as yes, technical impact partial. Vendor-released patch: Dancer2 2.2.0, which adds a halt check to the cleanup guard and makes hook compilation idempotent.
Denial of service in YARA 4.5.8 occurs when libyara deserializes a crafted compiled rule file (.yrc): malformed external-variable pointers or an out-of-range type field are not validated in the yr_rules_load/yr_rules_from_arena path, resulting in an invalid free in yr_rules_destroy() or a wild pointer dereference in yr_object_create(). Only deployments that load compiled rules from untrusted or third-party sources are exposed, since the assessed vector requires a user or process to actively load the file (UI:R) and no authentication (PR:N); the realistic outcome is a process crash rather than code execution (C:N/I:N/A:H). No public exploit code has been identified at time of analysis, EPSS is low at 0.21% (11th percentile), and the issue is not confirmed actively exploited (CISA KEV).
GPU memory exhaustion in vLLM through 0.29.0 allows remote, unauthenticated attackers to permanently leak GPU KV cache blocks by submitting completion requests containing multiple prompts whose concurrent child requests share a single Mooncake transfer ID. The leak is only reachable in prefill/decode (P/D) disaggregated deployments that have the Mooncake KV-transfer connector enabled - a non-default topology in which the vulnerable ownership bookkeeping runs - and orphaned blocks are never reclaimed until the vLLM process is restarted, progressively starving legitimate inference requests of GPU memory. No public exploit code has been identified at time of analysis and the flaw is not listed in CISA KEV, though the attack is network-reachable, low-complexity, and requires no authentication or user interaction (CVSS 4.0 8.7; independent assessment scores the availability-only impact as CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).
Memory exhaustion in vLLM through 0.29.0 lets remote, unauthenticated attackers crash the inference service by supplying an arbitrary 'tp_size' value inside the 'kv_transfer_params' field of requests to the OpenAI-compatible completion endpoints. Because kv_transfer_params is honored only when the server runs in a prefill/decode (P/D) disaggregated deployment using the NIXL KV-transfer connector, the attacker causes unbounded memory allocation in the decode worker that ends in a kernel OOM-kill and full loss of service availability; confidentiality and integrity are unaffected. No public exploit code was identified at time of analysis and there is no CISA KEV listing, but the flaw is trivially reachable over the network (CVSS 4.0 8.7, AV:N/AC:L/PR:N/UI:N/VA:H), and an upstream fix exists as pull request 51137.
Denial of service in vLLM through 0.29.0 lets unauthenticated remote attackers crash the EngineCore and halt all inference by feeding arbitrary remote host and port values through kv_transfer_params when the P2P secondary KV-offload tier is enabled. Each bogus peer address causes the server to allocate a ZeroMQ socket for an unreachable peer session; because no limit is enforced on concurrent sessions, the sockets accumulate until the context quota is exhausted and an uncaught ZMQError terminates the engine (CWE-770, unlimited resource allocation). Exploitation is gated on a non-default configuration - OffloadingConnector configured with TieringOffloadingSpec plus a p2p secondary tier - and availability is the only affected property; an upstream fix exists in pull request 51504, but no public exploit code has been identified at time of analysis.
Denial of service in vLLM through 0.29.0 allows an unauthenticated remote attacker to crash the NIXL decode worker by submitting a single OpenAI-compatible completion request containing multiple prompts of differing lengths together with kv_transfer_params. The crash occurs in NixlBaseConnectorWorker._apply_prefix_caching, where block-count mismatches between the decode and prefill sides hit a reachable assertion (CWE-617); the decode worker terminates and stays unavailable until manually restarted, so a low-effort request loop can repeatedly take serving capacity offline. Impact is confined to availability (CVSS 4.0 8.7, AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H), with no confidentiality or integrity effect, and exploitation is gated on a non-default prefill/decode DISAGGREGATED topology that uses the NIXL KV-transfer connector - standard single-node vLLM serving is not affected. No publicly available exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, though the trigger is a trivially crafted multi-prompt API call.
Denial of service in vLLM through 0.29.0 allows an unauthenticated remote attacker to crash the decode engine by sending a single inference request whose kv_transfer_params dictionary is incomplete, for example containing only {"do_remote_prefill": true} without the required remote_block_ids, remote_engine_id, remote_request_id, remote_host, and remote_port fields. The malformed metadata raises an uncaught KeyError inside EngineCore scheduling (CWE-248) during add_new_req_to_recv, terminating the decode engine and causing every subsequently routed request to fail until an operator manually restarts it, yielding a vendor CVSS 4.0 score of 8.7 (VA:H, C/I both N). Exposure is limited to deployments running prefill/decode disaggregated mode with the NIXL connector, which is a non-default serving configuration; standard single-node vLLM never processes kv_transfer_params on this path. No public exploit code and no confirmed active exploitation were identified at time of analysis, though the upstream fix and regression tests are public in PR #54807.
Path-based RBAC authorization bypass in Envoy Proxy lets an unauthenticated remote client reach protected backends such as /admin by appending a semicolon path parameter (e.g. /admin;x), because the router strips that suffix before route matching while the RBAC url_path matcher evaluates the untouched raw path. Exploitation is tightly gated rather than default: it requires a route configured with ignore_path_parameters_in_path_matching, a path-based RBAC rule (PathMatcher or UriTemplateMatcher) guarding the protected path, and a crafted request that still selects the protected route after stripping. All releases prior to 1.36.10, 1.37.6, 1.38.4, and 1.39.1 are affected; the vendor has published fixed releases, and no public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis.
Stored cross-site scripting in Envoy Proxy's admin statistics page lets an attacker run script in the admin interface's origin: the /stats?format=html endpoint (StatsHtmlRender) sanitizes statistic values but emits statistic names raw, so a data-plane component that folds attacker-supplied request path segments into dynamic stat names - notably grpc_stats with stats_for_all_methods enabled - can persist a script-bearing name that fires when an operator opens the page in a browser. Every release before 1.36.10, 1.37.6, 1.38.4, and 1.39.1 is affected; the independently assessed vector is CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N (7.4), i.e. unauthenticated remote influence over the injected text but multiple gating prerequisites plus required operator interaction, with impact scoped to the admin origin where privileged same-origin requests can then be issued. No public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV; exploitation is realistic only where the admin HTML endpoint is browser-reachable and a dynamic-stat-generating component is enabled.
Envoy Proxy releases prior to 1.36.10, 1.37.6, 1.38.4, and 1.39.1 can be crashed by a remote, unauthenticated attacker through its HTTP/3 datagram and Capsule Protocol handling (prerequisites: PR:N, no user interaction). When a request enters a stream-recreation path such as an internal redirect, the HttpDatagramHandler keeps a cached pointer to the original RequestDecoder; a subsequent HTTP/3 datagram invokes decodeData through that freed decoder, producing invalid virtual dispatch and process termination (CWE-416 use-after-free, CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H). Exploitation is gated on a non-default configuration - HTTP/3 (QUIC) downstream plus Capsule Protocol enabled, e.g. MASQUE connect-udp tunneling - combined with an internal-redirect route and precise frame sequencing; no public exploit code or CISA KEV entry was identified at time of analysis.
Unauthenticated remote attackers can exhaust memory and trigger an out-of-memory kill of Envoy Proxy by sending HTTP/2 requests that include a large Host header alongside an existing :authority pseudo-header, since the discarded Host value is copied but never charged against header size or count limits, and HPACK dynamic-table indexing lets an attacker repeatedly reference that large value across a bounded number of streams. All Envoy releases before 1.36.10, 1.37.6, 1.38.4, and 1.39.1 are affected, including both the nghttp2 and oghttp2 HTTP/2 codec implementations, and the flaw is reachable on any listener that terminates HTTP/2 with no authentication or user interaction required (CVSS 3.1 base 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, CWE-401). No public exploit code and no confirmed active exploitation have been identified at time of analysis, but the low complexity and lack of prerequisites make this a practical availability risk for internet-facing edge proxies; note the supplied "Authentication Bypass" tag is misleading - the impact is availability-only, with no confidentiality or integrity loss.
Unauthenticated remote clients can crash Envoy Proxy by sending a path-less CONNECT request when the ext_authz HTTP filter is configured to apply query_parameters_to_set or query_parameters_to_remove mutations and the external authorization service returns such a mutation. The crash is a null-pointer dereference in the ext_authz filter's Filter::onComplete path, producing a denial of service (CVSS 7.5, A:H) against the affected proxy process; impact is limited to availability, with no confidentiality or integrity loss. Exploitation is gated by two non-default configuration prerequisites - accepting path-less CONNECT and enabling ext_authz query-parameter mutation - and no public exploit code has been identified at time of analysis.
Denial of service in Envoy Proxy releases prior to 1.36.10, 1.37.6, 1.38.4, and 1.39.1, where the optional oghttp2 upstream HTTP/2 codec accepts a response trailer HEADERS frame that lacks the END_STREAM flag, causing Envoy to complete and deferred-delete the ActiveRequest while oghttp2 keeps the stream open. The resulting dangling reference in ClientStreamImpl (response_decoder_) can be dereferenced by a subsequent frame on that stream, freeing-then-using memory and crashing the Envoy process (CWE-20, CVSS 3.1 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - assessed independently at AC:H). Exploitation is remote and unauthenticated once preconditions hold, but it is limited to non-default configurations: the oghttp2 upstream codec must be explicitly enabled, the malformed trailers must be emitted by the upstream server Envoy proxies to (an attacker-controlled or compromised upstream, or injected frames on that connection), and the default nghttp2 codec rejects the malformed trailers outright. Vendor patches are available (1.36.10, 1.37.6, 1.38.4, 1.39.1); no public exploit code was identified and the issue is not in CISA KEV at time of analysis.
An access-control bypass in Envoy Proxy (all versions prior to 1.36.10, 1.37.6, 1.38.4, and 1.39.1) allows unauthenticated remote clients to reach routes that HTTP RBAC policies were configured to deny, resulting in disclosure of protected content. The flaw only materializes when a NEGATIVE (DENY) policy uses a safe_regex matcher against header values and a byte-oriented route matcher independently reads the raw header bytes; positive ALLOW regexes fail closed and exact, prefix, suffix, and contains matchers are unaffected. No public exploit code has been identified at time of analysis, and the vendor has released fixed versions, so real-world risk is driven almost entirely by whether a deployment uses that specific safe_regex-in-negative-policy configuration.
Request smuggling in Envoy Proxy allows an unauthenticated HTTP/2 client to embed a complete HTTP/1.1 request inside the data payload of an extended CONNECT (a generic, non-WebSocket HTTP upgrade) so that Envoy forwards that payload upstream before the upstream has accepted the upgrade, writes it unframed to a keep-alive HTTP/1.1 upstream, and returns the upstream socket to the shared pool with a smuggled response still queued - meaning a different, unrelated downstream client can subsequently be served the attacker's response. Every Envoy release prior to 1.36.10, 1.37.6, 1.38.4, and 1.39.1 is affected, but exploitation is configuration-dependent: the listener must proxy a generic non-WebSocket upgrade to an HTTP/1.1 upstream with backend keep-alive enabled, shared (non-per-downstream) connection pools, and max_requests_per_connection not set to 1; WebSocket upgrades, plain CONNECT, disabled backend keep-alive, per-downstream pools, and max_requests_per_connection=1 are explicitly out of scope for the demonstrated path. No public exploit code has been identified at time of analysis, and this CVE is not listed in CISA KEV.
Arbitrary command injection on Windows in the Perl distribution Email::Sender (Email::Sender::Transport::Sendmail versions before 2.602) lets an attacker who controls a From, To, or Cc header address execute commands as the sending process, because on MSWin32 the envelope sender and recipients are concatenated into a single command string that Perl's open() hands to a shell. The flaw is strictly Windows-only: on every other platform the transport uses open()'s list form and passes arguments directly to sendmail with no shell involved, so the injection path does not exist there, and exploitation additionally requires that the application use the sendmail transport rather than the SMTP transport and that the caller supply no explicit envelope (letting Email::Sender::Simple derive addresses from headers). The vendor CVSS of 9.8 (AV:N/AC:L/PR:N/UI:N) overstates real-world risk given that hard platform gate; our assessment uses CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, EPSS is low at 0.22% (13th percentile), SSVC records no observed exploitation with automatable attack and total technical impact, and no public exploit code was identified at time of analysis, though a vendor patch (2.602) and an upstream commit are public.
OpenBao versions prior to 2.6.0 fail to reject syntax-significant characters when templated identity data is substituted into ACL, PKI, and SSH policies, allowing an authenticated principal who can write that identity data to broaden path matching, obtain certificates for unauthorized domains, or add unauthorized SSH principals. Exploitation is gated on a non-default configuration: the policy must use templates that substitute attacker-modifiable identity metadata (for example {{identity.entity.metadata.domains}} or {{identity.entity.metadata.sans}}), and the attacker must already hold the capability to update that identity record (such as update on identity/entity), consistent with the assessed CVSS 3.1 vector AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N. Deployments whose templates rely solely on the randomly generated identity.entity.id value are not affected, there is no user interaction, and no public exploit code was identified at time of analysis.
Local privilege escalation in BleachBit on Windows lets an unprivileged local user turn an elevated cleaning operation into arbitrary privileged file deletion and, via Windows Installer rollback behavior, full SYSTEM privileges. The flaw affects BleachBit versions prior to 6.0.1 and is exploitable by an authenticated, unprivileged interactive user who wins a TOCTOU race while BleachBit runs with elevated rights in privileged Windows cleaning mode; the vector is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (7.8). No public exploit code was identified and there is no CISA KEV listing at time of analysis, so the practical risk is a genuine local privilege-escalation issue worth prioritizing on Windows hosts that run BleachBit with elevation.
An authorization flaw in the pki-core v2 REST ACL filter lets an authenticated member of the default Certificate Manager Agents group invoke profile-management operations reserved for Administrator-level accounts, so a request to POST /v2/profiles/raw that should require profiles.create is instead authorized under the lower-privileged profiles.approve permission. The root cause is that when a literal ACL key (profiles.create) and a wildcard ACL key (profiles.approve) both match, the filter picks the winner by lexicographic string comparison rather than by specificity, allowing the wildcard mapping to override the more specific literal one; CVSS 3.1 rates this 8.1 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N), with the highest threat to the confidentiality and integrity of the CA's issuance policy. Exploitation requires valid agent-level credentials and the default ACL configuration, and no public exploit code has been identified at time of analysis, so this is a privilege escalation inside an existing trusted role rather than unauthenticated access.
Heap-based buffer overflow in X.Org libXrender before 0.9.13 allows a malicious or compromised X server to inject and execute arbitrary code in attached X11 clients via a crafted response to the RenderQueryPictFormats request. This is a reverse-direction attack where the victim must actively connect a vulnerable X11 client (linked against libXrender < 0.9.13) to an attacker-controlled or hijacked X server - typical exposure is via SSH X11 forwarding to an untrusted host or a remote DISPLAY connection; local trusted X servers are not affected. No public exploit code has been identified at time of analysis, and exploitation is non-trivial (AC:H) with no attacker authentication required (PR:N), but an upstream fix is available and the CVE description identifies 0.9.13 as the fixed version boundary.
Heap-based buffer overflow in libX11 before 1.8.14 allows a malicious or compromised X server to corrupt memory in connecting X11 clients via a crafted XkbGetMap reply that overflows the key_sym_map. This client-side vulnerability has an inverted threat model: the attacker must control the X server the victim connects to, with exploitation requiring user interaction (UI:R) and high attack complexity (AC:H). CVSS 3.1 score is 7.5 High; no public exploit code has been identified at time of analysis.
Elevated-privilege container restoration in CRI-O 1.34 and later, including downstream Red Hat OpenShift Container Platform 4.17+, lets an authenticated Kubernetes user who can create a pod from a crafted checkpoint image bypass the destination pod's security context. The restored process keeps credentials, Linux capabilities, no_new_privs and seccomp state stored in the checkpoint instead of the destination configuration, allowing execution across the container security boundary. Exploitation requires non-default checkpoint/restore (CRIU) support to be enabled and RBAC permission to create pods from malicious checkpoints; no public exploit code is identified and no vendor-released fix is available at time of analysis, so the vendor CVSS 3.1 score of 8.8 overstates urgency given those prerequisites (our assessment raises attack complexity to High).
Arbitrary code execution in the npm front-matter parser gray-matter is reachable through its built-in JavaScript engine, which evaluates front matter with eval() whenever the document declares a js/javascript language fence. Any application that passes attacker-influenced markdown or front-matter text into gray-matter's parse call can be induced to run attacker-supplied JavaScript in the Node.js process - the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, 9.8) rates this as unauthenticated remote code execution, with the practical caveat from our assessment that the attack surface is gated by whether the host application exposes gray-matter parsing to untrusted content. Affected coverage is broad rather than version-specific: the reporter states all versions are impacted and verified 4.0.3, while there is no CISA KEV entry, no confirmed public exploit code, and a low EPSS of 0.17% (7th percentile) indicating limited observed exploitation pressure at time of analysis.
Command injection in CrossWire Xiphos 4.3.2 and earlier lets a local attacker execute arbitrary shell commands with the privileges of the user running the application by placing shell metacharacters in data that Xiphos later interpolates into unsanitized popen() shell pipelines. Two code paths are involved: the personal-commentary rename action (on_rename_perscomm_activate in src/gtk/menu_popup.c), where the module section name is spliced into a cd/sed command, and the separate-image viewer (show_separate_image in src/main/url.cc), where an image filename is spliced into an external viewer's command line. Exploitation requires the victim to trigger one of those actions on attacker-supplied data (a crafted module or image file), the impact is confined to the victim's own account because no privilege escalation is demonstrated, and publicly available exploit code exists (SSVC records exploitation as 'poc'), although the issue is not in CISA KEV and EPSS is low at 0.15% (5th percentile).
Use-after-free in Suricata before 8.0.7 can crash the HTTP/2 inspection engine when a transaction is inspected by rules that use http.response_header both with and without a transform. The flaw is remotely triggerable by HTTP/2 server responses traversing the sensor, requires no authentication per the CVSS vector, and the vendor has released 8.0.7 as the fix. No public exploit code or confirmed active exploitation was identified at time of analysis; the assessed impact is primarily denial of service and limited memory disclosure, not confirmed code execution, and exploitation depends on the specific dual-rule HTTP/2 configuration.
Suricata 8.x before 8.0.7 contains a type confusion vulnerability in the DoH2 (DNS over HTTPS version 2) parser that can result in an invalid free, leading to memory corruption. An unauthenticated remote attacker can trigger this by sending a crafted DoH2 request that performs an HTTP1-to-HTTP2 upgrade through a monitored network, potentially causing a crash or arbitrary code execution. The vulnerability is exploitable by default in 8.x sensors because the doh2 app-layer protocol is enabled out-of-the-box; no public exploit code has been identified at time of analysis, but the severity is high.
Remote code execution in Mistral Vibe before 2.25.5 allows an attacker to run arbitrary shell commands with the privileges of the user running the tool, because worktree creation executes a repository's own git hooks - notably the post-checkout hook and the fsmonitor command - before any workspace trust validation takes place. The attack requires the victim to deliberately open, clone, or check out an attacker-controlled repository (user interaction is mandatory, and the request itself is unauthenticated per the CVSS PR:N vector), and code execution is bounded by the permissions of the Vibe user, with no privilege escalation or server-side attack surface. There is no public exploit identified at time of analysis and the flaw is not confirmed as actively exploited; a vendor-released patch in 2.25.5 addresses the ordering bug.
Malformed UTF-16 decoding in libexpat through 2.8.4 lets remote attackers hide XML markup from the parser: a lone high surrogate paired with the following code unit is accepted as a valid surrogate pair, so a character such as '<' is consumed as part of the pair and never tokenized. Only applications that parse UTF-16-encoded XML (little- or big-endian) from an untrusted source are affected - the dominant UTF-8 input path is not exploitable - and meaningful integrity impact additionally requires a downstream filter, sanitizer, or validator that trusts the parsed structure and therefore sees different markup than Expat exposes. No public exploit has been identified at time of analysis; an upstream fix is available in the Expat repository (PR #1282, commit ff6e1d7e750bbe245178f51a47a965dc8342861a), reported via VulnCheck.
Information disclosure in Exim before 4.100.1 allows attackers who control or can impersonate a proxy in the configured proxy_protocol_hosts set to read uninitialized stack memory when PROXY Protocol is enabled, but only in non-default deployments and with limited confidentiality impact. This is a conditional flaw requiring attacker control of a trusted proxy; stock Exim installations without Proxy-Protocol are unaffected. No public exploit code or evidence of active exploitation was identified at time of analysis.
Serialization of Node.js Buffer objects in the JavaScript library devalue 5.1.0 through 5.9.2 leaks unrelated process memory: when stringify, stringifyAsync, or uneval encounters a Buffer, it emits the view's entire backing ArrayBuffer instead of only the visible bytes, and because small Buffers are carved from Node's process-wide shared allocation pool, the serialized output can include up to roughly 64 KB of memory belonging to other in-flight requests. Any server-side-rendered application that serializes a Buffer into HTML without authentication - a SvelteKit or Nuxt page whose load() returns a small Buffer or reads a small file - can therefore publish another user's request body or Authorization header in a public response, and the flaw triggers on every such render because it occurs during serialization rather than parsing, so the library's parse/unflatten prototype-pollution and denial-of-service guards provide no protection. Unauthenticated remote attackers need no user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, 7.5), the affected CPE is cpe:2.3:a:sveltejs:devalue:*, and no public exploit code or confirmed active exploitation was identified at time of analysis.
Memory-exhaustion denial of service in SGLang through 0.5.20 allows anyone who can reach the decode engine's internal ZMQ rank port to terminate the serving process by sending a single STAGING_REQ frame carrying an extremely large chunk_idx value. The flaw applies only to deployments running prefill/decode disaggregation - a non-default, multi-engine serving topology - and requires network reachability to the inter-rank ZMQ port that normally carries unauthenticated traffic on a trusted cluster network; when that port is bound to loopback or an isolated back-end network, the issue is not reachably exploitable. No public exploit identified at time of analysis, and the impact is confined to availability: the scheduler allocates memory until the system runs out and the process is killed, with no data exposure or code execution.
Remote denial of service in osmo-iuh's HNBGW (Home NodeB Gateway) lets a network-reachable peer on the Iuh interface crash the process by sending a RANAP connection-oriented direct-transfer message carrying an arbitrarily sized NAS-PDU, which trips a reachable assertion in ranap_handle_co_dt(). Per the CVE description the affected range is osmo-iuh 1.10.0 through 1.14.5, although the ENISA EUVD entry lists a much narrower 0.1.0 <1.8.0 scope and the supplied CPE points at osmocom:osmo-bsc, so the exact affected version set should be confirmed against the vendor advisory. Impact is availability-only (CVSS 3.1 base 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H; SSVC Technical Impact: partial) with no confidentiality or integrity loss; there is no CISA KEV listing, no public exploit code identified at time of analysis, and EPSS is low at 0.17% (7th percentile).
Remote denial of service in Osmocom osmo-bsc 1.0.1 through 1.14.1: a heap-based buffer overflow in ipaccess_proxy_read_msg() is triggered when a crafted IPA frame carries an attacker-controlled length value that is used without adequate validation against the actual buffer size. The issue is remotely reachable and requires no authentication or user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N) from any host able to talk to an osmo-bsc instance with the ipaccess proxy component deployed, and the assessed impact is availability-only (C:N/I:N/A:H), meaning a successful trigger corrupts heap memory and crashes the process. There is no public exploit identified at time of analysis and EPSS is a low 0.14% (4th percentile), consistent with the deployment reality that BSC signaling paths such as the IPA/A-bis proxy are normally confined to segmented, non-public operator networks.
Prototype pollution in the deepmerge JavaScript library (all versions through 4.3.1) allows an attacker who controls a source object passed into a merge operation to inject properties such as '__proto__', 'constructor', or 'prototype' into the resulting object's prototype chain. The impact is latency-dependent: applications that merge untrusted data (for example, a JSON request body) and then read properties without own-property checks will silently inherit attacker-chosen values, which can corrupt application logic, bypass authorization checks, or influence downstream behaviour. The flaw is a library primitive rather than a standalone exploit, and no public exploit code was identified at time of analysis; the vendor CVSS 4.0 score of 8.7 reflects integrity impact only (VC:N/VA:N), and an independent assessment rates it considerably lower (CVSS 3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N) because exploitation requires the consuming application to both pass attacker-controlled source objects and perform unchecked inherited-property reads.
Denial of service in the CSSOM JavaScript library through 0.5.0 allows unauthenticated remote attackers to terminate a parsing process by supplying a stylesheet declaration named 'length', a reserved property name that is not validated and therefore overwrites the internal declaration counter; the corrupted counter then drives an oversized memory allocation when cssText is serialized, crashing the process. Exploitation is conditional rather than automatic: the host application must feed attacker-controlled CSS into CSSStyleDeclaration.setProperty() or stylesheet parsing and must later serialize that declaration via cssText, so deployments that only parse trusted first-party CSS, or that never serialize untrusted input, are not exposed. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV; the provided CVSS 4.0 score of 8.7 (assessed as CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) reflects a high availability-only impact with no confidentiality or integrity effect, and the library itself is not network-exposed.
Cross-client information disclosure in http-cache-semantics through 4.2.0 allows remote, unauthenticated attackers to receive cached responses that were generated for other users. The library's _varyMatches() function performs byte-for-byte comparison of Vary header values and therefore fails to treat a wildcard 'Vary: *' directive as a prohibition on shared-cache reuse, so a request for a URL previously fetched by someone else can be satisfied from cache with that other client's sensitive per-user data. Exploitation is conditional and non-deterministic - it requires a shared, multi-user cache deployment and an origin that emits wildcard Vary on cacheable responses - which is consistent with the vendor CVSS 4.0 score of 8.2 with AC:H and AT:P; no public exploit code has been identified at time of analysis.
Denial of service in source-map-js up to and including 1.2.1 allows an attacker who can supply an indexed source map to hang the Node.js process: the library reads the per-section offset.line value without bounds checking, so an arbitrarily large integer forces a long synchronous loop that blocks the event loop and starves all other requests. The flaw (CWE-1284, improper validation of a specified quantity) is reachable only where a service actually parses attacker-controlled maps - for example an online transpiler, upload-accepting bundler service, or error/stack-trace resolver - since source maps are normally trusted build-time artifacts; the assessed CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H) reflects that data-flow prerequisite, and no public exploit was identified at time of analysis. Impact is availability only; despite the 'Information Disclosure' tag in some feeds, there is no confidentiality or integrity loss in the assessed vector.
TLS certificate validation bypass in AnyIO (pip/anyio) versions before 4.14.2 lets an attacker who already holds an on-path man-in-the-middle position impersonate a server named with a non-ASCII internationalized domain name. AnyIO's TLSStream.wrap() encoded the target host name with IDNA 2003 (via the Python standard library) instead of IDNA 2008 before matching it against the peer certificate, so a host like 'faß.de' was compared against the certificate for 'fass.de' - an attacker can obtain a legitimately CA-issued certificate for that wrong domain and have it validate on the client. Exploitation requires all three of: an application calling connect_tcp(tls=True) or TLSStream.wrap() with an affected unicode host name, a pre-existing connection hijack/redirect the vulnerability does not itself provide, and attacker acquisition of a valid certificate for the IDNA 2003-encoded name; ASCII-only host names are unaffected. No public exploit code has been identified at time of analysis, and patched version 4.14.2 is available.
Missing authorization enforcement in Google Chrome builds earlier than 154.0.8037.57 (classified CWE-862 and tagged as an authentication bypass) lets an attacker defeat an access-control decision in the browser, with the impact scored as high confidentiality and high integrity loss (CVSS 3.1 base 8.1, AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N). The flaw is network-delivered and requires no authentication or prior privileges, but exploitation is not silent: the victim must navigate to or render attacker-controlled web content (UI:R), which keeps the practical attack path dependent on user browsing behavior rather than on a remotely reachable service. Google has shipped the fix in Chrome 154.0.8037.57 and the issue is tracked as ENISA EUVD-2026-89222 / Chromium issue 540265100; no public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV, so there is no confirmed active exploitation.
An out-of-bounds memory write in Google Chrome allows an unauthenticated, remote attacker to corrupt memory and potentially execute arbitrary code or crash the browser when a victim opens a crafted web page, as reflected by the CVSS 3.1 vector AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H (9.6, scope-changed). The flaw is classified as CWE-787 (out-of-bounds write) and is addressed by the vendor's stable channel update for desktop, with the fix credits originating from the Ubuntu vendor reporting channel, meaning downstream Chromium packages are also in scope. At time of analysis there is no public exploit identified, no CISA KEV listing, and no EPSS data provided; however, because browser memory-corruption bugs of this class are historically attractive to exploit developers, this remains a high-priority patching item despite the absence of exploitation telemetry.
The affected product and the nature of the security impact for CVE-2026-95325 cannot be established from the intelligence available at time of analysis. The only signal present is that the entry was reported by the vendor source 'ubuntu', with no description, CVSS score or vector, CWE mapping, CPE identifiers, references, EPSS score, or KEV status supplied; the independent assessment accordingly classifies this as a data-void entry with no analyzable signals. No public exploit identified at time of analysis, and there is no basis to characterize the attack vector, authentication requirements, or affected versions.
Ubuntu Linux is the only product attributable to CVE-2026-95319, and the sole intelligence signal available is a vendor:ubuntu report with no accompanying advisory text, version range, or affected component. No description, CVSS score, CVSS vector, CWE classification, CPE string, EPSS score, KEV status, or reference link was supplied, so the vulnerability class, attack vector, privilege requirements, and impact cannot be characterized. No public exploit code has been identified at time of analysis, but this reflects absent data rather than a confirmed absence of exploitation, and the entry must be treated as unassessable until the upstream NVD or Ubuntu security advisory is retrieved.
Cross-site request forgery in Google Chrome on desktop lets a remote, unauthenticated attacker achieve high confidentiality, integrity and availability impact against a victim who is persuaded to visit or interact with an attacker-controlled page (CVSS 3.1 vector AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 8.8). Only Chrome installations older than 154.0.8037.57 are affected, and Google has shipped a stable channel fix in that build, with the issue tracked upstream as Chromium issue 511791538 and Ubuntu listed among the reporters. No public exploit code has been identified and the flaw is not in CISA KEV, but note that the official description is empty and the CWE-352 label is hard to reconcile with the full C/I/A impact claimed, so the exact triggering feature remains unconfirmed.
Race condition in Google Chrome's stable channel allows a remote, unauthenticated attacker who persuades a user to interact with crafted content to win a time-of-check/time-of-use window and affect data beyond the vulnerable component's security scope. The CVSS 3.1 base score of 8.0 (AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N) reflects high confidentiality and integrity impact with no availability impact, tempered by high attack complexity; no public exploit code or CISA KEV entry was identified at time of analysis. The flaw is addressed in the 154.0.8037.57 stable channel update, and while the vendor feed tags it Information Disclosure, the scoring indicates a broader boundary-crossing defect, so this is best treated as a moderately high-priority browser issue with partly inferred impact.
Improper input validation in Google Chrome before 154.0.8037.57 allows unauthenticated remote attackers to achieve high confidentiality, integrity, and availability impact with a scope change, though exploitation requires the victim to visit attacker-controlled web content and overcome high attack complexity. The flaw, tracked as CVE-2026-95341 with a CVSS 8.3 base score, affects default installations of Chrome on all platforms and could permit renderer-level code execution or sandbox escape; no public exploit identified at time of analysis. Vendor-released patch 154.0.8037.57 addresses the issue.
Use-after-free memory corruption in Google Chrome allows remote attackers to corrupt memory and potentially execute code beyond the browser's normal security boundaries when a victim loads attacker-controlled web content. The flaw carries a CVSS 9.6 with vector AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H, meaning no authentication is required, the attack is network-delivered, and the scope change plus full confidentiality, integrity, and availability impact indicate a flaw that can affect resources beyond the vulnerable component - consistent with a renderer sandbox escape. Exploitation requires the victim to visit a malicious page or render a malicious embedded resource such as an ad or iframe; at time of analysis there is no public exploit identified, but the vendor has released a patched stable-channel build and defenders should treat untrusted browsing on unpatched Chrome as high risk.
Type confusion in Google Chrome's core rendering code allows remote attackers to corrupt memory and execute arbitrary code inside the browser renderer, affecting Chrome builds prior to 154.0.8037.57 on all platforms. Exploitation requires the victim to load attacker-controlled web content (a malicious or compromised page), matching the CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H profile - no credentials are needed, and default configurations are exposed because the flaw sits in normal rendering rather than an optional feature. At the time of analysis there is no CISA KEV listing and no public exploit identified at time of analysis; the impact is contained to the sandboxed renderer (S:U), so full host compromise would require a separate sandbox escape not described in this record, but the integrity and confidentiality impact within the renderer is high and the issue is rated 8.8.
Type confusion in Google Chrome's renderer allows remote attackers to corrupt memory and potentially achieve code execution inside the browser by convincing a victim to open a crafted web page; the attack is network-delivered, requires no authentication (PR:N), and has low complexity, with the only meaningful barrier being that the user must interact with attacker-controlled content (UI:R). A vendor patch is available per the September 2026 stable-channel update, and no public exploit code or confirmed active exploitation was identified at time of analysis, so the high priority here is driven mainly by Chrome's ubiquity rather than observed attacks. Because the CVSS scope is unchanged (S:U), full-system compromise as scored would likely require chaining this bug with a separate sandbox-escape vulnerability, while on its own the flaw is expected to yield renderer-level memory corruption, information disclosure, and potential arbitrary code within the sandboxed process.
Risk cannot be meaningfully assessed from the supplied data: CVE-2026-95283 is recorded only as a vendor-reported entry from Ubuntu, with the description marked '[Unknown description]' and no CVSS score, CVSS vector, CWE, CPE, or affected source package provided. Because the impacted component, deployment mode, and attack surface are all unidentified, no statement can be made about what an attacker could achieve, which versions are affected, or what preconditions (authentication, user interaction, configuration) would be required. There is no KEV listing and no public exploit code identified at time of analysis, so the entry should be treated as an unassessed tracking record rather than a confirmed exploitable issue.
Heap-based buffer overflow in Google Chrome desktop (stable channel) allows a remote, unauthenticated attacker to corrupt heap memory when a victim renders attacker-controlled web content such as a malicious page, iframe, or ad, yielding high impact to confidentiality, integrity, and availability with a changed scope that suggests effects can extend beyond the initially affected component. Exploitation requires user interaction (UI:R) - the victim must load the hostile content - but needs no credentials (PR:N), is network-reachable (AV:N) and low complexity (AC:L), making actively browsing, unpatched endpoints the realistic exposure. No public exploit has been identified at time of analysis; the referenced Chrome stable channel advisory and Chromium issue 551573368 confirm a vendor fix, and the independent assessment rates this a genuine high priority at CVSS 9.6.
Risk cannot be meaningfully assessed from the available data. CVE-2026-95281 is tracked in the Ubuntu security database, which establishes only that it affects software shipped as a package within the Ubuntu distribution; the upstream project, the vulnerable component, and the affected Ubuntu releases are all unspecified. No description, CVSS vector, CWE, CPE, KEV status, or exploit data was provided, and no public exploit has been identified at time of analysis, so the attack vector, privilege requirements, and user-interaction prerequisites remain unknown and must be sourced from the corresponding Ubuntu Security Notice or the NVD entry.
No technical details are available for CVE-2026-95338: the description field is empty and no CVSS score, CVSS vector, CWE classification, CPE string, or affected package name was supplied alongside the record. The only identifying signal is that the issue was reported under the vendor:ubuntu source, indicating it is tracked as a vulnerability in a package distributed through Ubuntu's repositories and handled via the Ubuntu Security Notice process. Risk cannot be meaningfully assessed from the available data, and there is no public exploit identified at time of analysis; exploitation prerequisites, impact, and affected versions must be obtained from the Ubuntu Security Notice for this CVE before any triage decision is made.
A missing-authorization flaw (CWE-862) in Google Chrome desktop builds prior to 154.0.8037.57 can be triggered by an unauthenticated local attacker with no user interaction, and the assessed CVSS vector (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 8.4) rates confidentiality, integrity and availability impact as high, consistent with the 'Authentication Bypass' tagging applied by the reporting vendor. The local attack vector and absence of a user-interaction requirement mean the attacker must already have some form of local execution context on the target host, which sharply constrains mass remote exploitation; no public exploit code has been identified at time of analysis and EPSS is low at 0.24% (13th percentile). Exploitation is limited to unpatched builds and is fully mitigated by the vendor-released fix in Chrome 154.0.8037.57, so this should be handled as a moderate-priority patch rather than an emergency, though the 8.4 score and high CIA impact still warrant prompt update cycles.
Ubuntu Linux is the only product implicated by the available reporting for CVE-2026-95311, a record attributed to the Ubuntu vendor security team, but the vulnerability description is unpublished and no CVSS score or vector, CWE classification, CPE identifier, EPSS estimate, or CISA KEV entry accompanies it, so the affected component, version range, and attack vector cannot be stated. No public exploit code has been identified at time of analysis, and there is no evidence of confirmed active exploitation. Risk cannot be meaningfully assessed from the provided data; the only actionable intelligence is the vendor attribution, which indicates Canonical is coordinating the record and that the Ubuntu Security Notices feed and the upstream advisory should be monitored for the eventual disclosure.
Use-after-free memory corruption in Google Chrome desktop builds prior to 154.0.8037.57 allows a remote, unauthenticated attacker to trigger heap memory corruption in the browser by convincing a victim to load attacker-controlled web content - a single page navigation is sufficient (UI:R, PR:N, AV:N). The flaw is rated CVSS 9.6 with a scope change (S:C), indicating the corruption can affect resources beyond the initially vulnerable component; no authentication, prior privileges, or non-default configuration is required, though exploitation hinges entirely on user interaction with a malicious or compromised page. Google has already shipped a fixed build (154.0.8037.57) on the stable channel, and no public exploit code or confirmed active exploitation was identified at time of analysis, making this a genuine high-priority patch-and-update item rather than an emergency zero-day response.
Use-after-free memory corruption in Google Chrome builds prior to 154.0.8037.57 allows a remote, unauthenticated attacker to corrupt memory and potentially execute code within the browser renderer by persuading a victim to load attacker-controlled web content (CVSS 3.1 base 8.8, AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). No public exploit code has been identified at time of analysis and the flaw is not listed in CISA KEV. Exploitation requires the victim to open a malicious page or attacker-embedded content in a trusted site, and because the assessed scope is unchanged (S:U) the impact is initially confined to the renderer sandbox, so full host takeover would require a separate sandbox escape; Google has shipped a fixed build that is distributed through Chrome auto-update, shrinking the exposure window on kept-current fleets.
Use-after-free memory corruption in Google Chrome's desktop stable channel lets remote, unauthenticated attackers achieve high-integrity/high-availability impact against a victim who simply renders attacker-controlled web content - the attacker must first convince the user to visit a malicious or compromised page (or load a malicious ad/iframe), which is why the assessed vector carries UI:R despite PR:N. Per our independent assessment, a practical exploit must win a heap-grooming race to reclaim the freed object and, because of the scope change (S:C), chain a further sandbox escape to fully realize the 9.6 severity, so exploitation is possible but not trivial. A vendor fix is available in the referenced Chrome stable channel update, and no public exploit code has been identified at time of analysis; the specific vulnerable component and exact fixed build are not disclosed in the available data.
Heap-based buffer overflow in Google Chrome builds earlier than 154.0.8037.57 allows unauthenticated remote attackers to corrupt memory when a victim loads attacker-controlled web content, with a CVSS base score of 9.6 (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H) reflecting scope change and potential high confidentiality, integrity, and availability impact. Exploitation requires user interaction - visiting a malicious site, a compromised page, or a malicious ad - and full host compromise would most likely require chaining this renderer-process overflow with a separate sandbox-escape bug rather than this flaw alone. Risk signals conflict in the usual browser-bug pattern: EPSS is only 0.29% (19th percentile), there is no CISA KEV listing, and no public exploit identified at time of analysis, while Chrome's silent auto-update rapidly shrinks the vulnerable population and a vendor patch is already available.
Memory corruption via use-after-free in Google Chrome allows remote code execution or sensitive data disclosure in the renderer when a victim loads attacker-controlled web content in any version earlier than 154.0.8037.57. The flaw is network-reachable, low-complexity and requires no authentication (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 8.8 High), but it does require the user to open a malicious page, ad or iframe, and because the scope is Unchanged the immediate impact stays inside the sandboxed renderer, so full host compromise realistically needs a second, chained sandbox-escape bug. There is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV); a vendor patch is available in Chrome 154.0.8037.57.
An authorization-bypass flaw in Google Chrome desktop builds prior to 154.0.8037.57 lets remote attackers escape a security boundary by having the victim load crafted web content in the browser. Successful exploitation crosses a sandbox boundary (S:C) and can compromise confidentiality, integrity and availability of the affected system, but the CVSS vector (AC:H, UI:R) means the attacker must satisfy specific timing or memory-state conditions and the user must actively visit or interact with the malicious page. No confirmed active exploitation (not in CISA KEV), no public exploit code identified at time of analysis, and a vendor patch is available, so prioritization should reflect a high-severity but hard-to-trigger client-side issue rather than an imminent mass-exploitation event.
Information disclosure in Google Chrome desktop builds earlier than 154.0.8037.57 lets an attacker who shares a local network segment with the victim trigger a flaw that the assessed CVSS scores as high impact across confidentiality, integrity, and availability (CVSS 8.0, AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). The attacker needs no authentication or elevated privileges (PR:N), but must be positioned on the same adjacent L2 segment as the target (AV:A) and must get the victim to load attacker-influenced content (UI:R) - a combination that substantially constrains mass or opportunistic exploitation. An official fix is already available on the stable channel and no public exploit code has been identified at time of analysis, so risk here is driven primarily by Chrome's ubiquity and by unpatched client exposure rather than by observed exploitation activity.
CVE-2026-95277 is currently an effectively empty record: no description, CVSS score, CVSS vector, CWE mapping, affected product, version range, or CPE data has been published, and the only intelligence signal is attribution to the Ubuntu vendor reporting channel. Because the vulnerability class, attack vector, authentication requirements, and impacted component are all unknown, risk cannot be meaningfully assessed from the available data and no exploit status can be confirmed - there is no public exploit identified at time of analysis, and the entry is not listed as confirmed actively exploited (CISA KEV). Organizations should treat this identifier as a placeholder to be re-triaged once Ubuntu publishes a corresponding security notice (USN) or the upstream CVE record is populated.
Out-of-bounds memory write in Google Chrome (desktop builds) lets remote, unauthenticated attackers corrupt browser memory when a victim loads attacker-controlled web content. The vendor CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:R/S:U with C:H/I:H/A:H (base 8.8), so the only prerequisite is that a user navigates to or renders a malicious page, and because the vector is scope-unchanged the memory corruption is expected to remain within the renderer/browser process rather than granting an inherent sandbox escape. The underlying flaw is an out-of-bounds write (CWE-787) in Chrome builds predating the vendor's September 2026 stable channel fix; patched builds are not affected, and no public exploit code or confirmed active exploitation was identified at time of analysis.
Use-after-free memory corruption in Google Chrome desktop builds earlier than 154.0.8037.57 (CWE-416) allows remote attackers to corrupt memory and potentially achieve code execution inside the renderer process when a victim opens a malicious or compromised web page. The flaw is remotely reachable with low attack complexity and no privileges required (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, 8.8), but it hinges on user interaction and, because scope is unchanged, exploitation is contained to the sandboxed renderer; full host compromise realistically requires chaining a separate sandbox-escape bug. There is no confirmed active exploitation and no public exploit identified at time of analysis, so the elevated priority is driven by Chrome's ubiquity and the reliability of memory-safety bugs in this class rather than by observed attacks; vendor patches are already available.
Google Chrome stable builds earlier than 154.0.8037.57 contain a race condition (CWE-362) that a remote attacker can trigger by getting a victim to load attacker-controlled web content, yielding high confidentiality, integrity, and availability impact within the browser's renderer sandbox. No authentication or special browser configuration is required (CVSS 8.8, AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), though user interaction - visiting or rendering hostile content - is the primary exploitation prerequisite, and a separate sandbox escape would be needed to reach the host. Exploitation status: no public exploit identified at time of analysis, and there is no CISA KEV listing; the vendor has shipped a fixed release.
Google Chrome desktop builds earlier than 154.0.8037.57 are affected by an improper input validation flaw (CWE-20) rated CVSS 8.3 (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H), in which an unauthenticated remote attacker who persuades a user to load attacker-controlled web content can potentially achieve high confidentiality, integrity and availability impact that crosses a browser security boundary. Although the public tagging labels this issue as information disclosure, the assessed vector indicates broader high impact across all three CIA dimensions combined with a scope change (S:C), consistent with escaping the Chrome renderer sandbox. Exploitation is constrained by mandatory user interaction and high attack complexity, no public exploit has been identified at time of analysis, and Google has already shipped the fix in the stable channel, so auto-updating installations are remediated on restart.
Risk cannot be meaningfully assessed for CVE-2026-95299 because the vulnerability record contains no description, no CVSS score or vector, no CWE mapping, and no CPE/product identifiers; the only attributable data point is that the issue was reported by the vendor Ubuntu. Consequently the affected component, the attack surface, and any prerequisite conditions remain unknown, and no public exploit has been identified at time of analysis. Analysts should treat this identifier as unresolved rather than low-risk: an empty record frequently reflects a placeholder or embargoed entry that is populated later, so the absence of detail is not evidence of low severity.
Improper input validation in Google Chrome before 154.0.8037.57 can be triggered when a victim loads attacker-controlled web content, yielding a scope-changed impact rated high for confidentiality, integrity, and availability (CVSS 8.3). Exploitation is network-reachable without credentials (PR:N) but demands victim interaction (UI:R) plus non-trivial preconditions such as specific memory state, heap grooming, or timing windows (AC:H), and the affected component is undisclosed because chromium issue 517730821 is access-restricted. No public exploit code and no confirmed active exploitation were identified at time of analysis; a vendor patch is available in the Chrome stable channel at 154.0.8037.57.
A use-after-free in Google Chrome desktop can be triggered when a victim renders attacker-controlled web content, allowing memory corruption that may lead to code execution or disclosure of sensitive in-process data. Affected are Chrome desktop builds on Windows, macOS, and Linux prior to the September 2026 stable channel update; the CVSS vector (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H, 9.6) requires no authentication or privileges but does require the victim to open or load a malicious or compromised page, and the S:C metric indicates the attack can affect a component beyond the one that is corrupted. Vendor-released patch available; no public exploit identified at time of analysis, and the reporting originator is Ubuntu.
Use-after-free memory corruption in Google Chrome builds earlier than 154.0.8037.57 allows a remote, unauthenticated attacker to corrupt memory in the browser by having a victim load attacker-controlled web content, yielding code execution with high confidentiality, integrity, and availability impact (CVSS 3.1 base 8.8, CWE-416). Exploitation is network-reachable with low complexity and requires no credentials, but is gated on user interaction (UI:R) - the victim must visit a malicious page or view attacker-controlled content such as a malicious ad or iframe. Because scope is unchanged (S:U), the primitive is contained within the renderer process, so full host compromise realistically requires chaining an additional sandbox-escape vulnerability; a fixed build is already available and there is no public exploit identified at time of analysis (no CISA KEV listing, no confirmed in-the-wild activity reported in the supplied intelligence).
Google Chrome on the desktop stable channel carries a vendor-patched security defect tracked as CVE-2026-95347, disclosed through Google's Chrome Releases stable-channel update in September 2026. The actual impact is currently undetermined: no description, CVSS score or vector, CWE classification, or affected version range has been published, so the vulnerability class, whether attackers must be authenticated, and whether user interaction (such as visiting a crafted page) is required cannot be confirmed from available data. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and no EPSS probability or SSVC decision data exists to refine the risk; this should be treated as a patch-priority item pending the details in the vendor advisory.
Use-after-free memory corruption in Google Chrome before 154.0.8037.57 allows a remote, unauthenticated attacker to potentially escape the browser's renderer sandbox by persuading a victim to visit attacker-controlled web content. Exploitation requires mandatory user interaction (UI:R) and a high-complexity precondition such as precise heap grooming or a timing race (AC:H), and no public exploit has been identified at time of analysis. Google has issued a vendor-released patch in version 154.0.8037.57 that removes the vulnerable code path.
Heap-based buffer overflow (CWE-122) in Google Chrome's stable channel, addressed in the September 2026 desktop stable-channel update, lets remote, unauthenticated attackers corrupt heap memory in a vulnerable build and potentially escape the browser's renderer sandbox for full confidentiality, integrity, and availability impact (CVSS 3.1 base 9.6, S:C). Exploitation requires the victim to interact with attacker-controlled web content - typically visiting a malicious page or rendering a hostile ad - so the practical window depends on how quickly users and Linux distributions apply the update. No public exploit identified at time of analysis, and the issue is not listed in CISA KEV; details remain limited because the referenced Chromium issue tracker entry is access-restricted.
Use-after-free in Google Chrome builds prior to 154.0.8037.57 allows remote, unauthenticated attackers to corrupt memory when a victim loads attacker-controlled web content, with potential for information disclosure and code execution. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 8.8) indicates low-complexity, network-reachable exploitation that is gated only by user interaction, and because scope is unchanged (S:U) any initial code execution is confined to the renderer sandbox, so full host compromise would require chaining a separate sandbox escape. No public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis, and a vendor patch in Chrome 154.0.8037.57 is available.
Type confusion in Google Chrome builds prior to 154.0.8037.57 lets a remote attacker who convinces a victim to load attacker-controlled web content corrupt memory inside the renderer and potentially achieve code execution in that process. The flaw is rated CVSS 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, CWE-843), meaning no authentication or privileges are required but exploitation is not zero-click: the victim must render a malicious page, and because scope is unchanged the initial compromise is confined to the renderer sandbox unless chained with a separate sandbox escape. No public exploit code has been identified at time of analysis and the issue is not listed as confirmed actively exploited (CISA KEV); a vendor-released patch is available in Chrome 154.0.8037.57.
Use-after-free memory corruption in Google Chrome desktop builds prior to 154.0.8037.57 allows remote attackers to achieve high-integrity and high-confidentiality impact against a victim who loads attacker-controlled web content and performs some interaction with it, but exploitation is not trivially repeatable: with AC:H it depends on winning a race or reliably grooming heap layout rather than a single deterministic trigger. The flaw is reachable without authentication (PR:N) and the vector's scope change (S:C) indicates the assessed impact crosses a component boundary, yet no public exploit code has been identified at time of analysis and there is no CISA KEV listing, so this should be treated as a high-priority patching item rather than a confirmed in-the-wild threat. A vendor patch is available.
Authentication bypass in Google Chrome prior to 154.0.8037.57 allows an attacker with local access to the machine to slip past an authorization check in a browser component, yielding high confidentiality, integrity, and availability impact. The assessed CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:N) means no privileges and no user interaction are needed once local access exists, so the realistic prerequisite is the ability to execute or otherwise interact with the vulnerable Chrome component on the host rather than reaching it over the network; a purely remote, unauthenticated web-based attack is not supported by the available data. Exploitation signals are currently weak and non-urgent: EPSS is only 0.22% (12th percentile), there is no CISA KEV listing, and no public exploit code was identified at time of analysis, while the vendor has shipped a fixed build. Note that the affected feature or component is not named in the available data because no vendor description was published, so the exact local precondition should be confirmed against the Chrome release advisory.
Timing-based leakage of the single recovery token in OpenBao lets a remote, unauthenticated attacker who can reach the instance while it is running in highly privileged recovery mode recover that token and then read or modify data on the OpenBao instance. The exposure is constrained to the transient recovery-mode break-glass state rather than the normal serving configuration, and exploitation requires collecting a large volume of low-noise timing samples against the recovery endpoint (reflected in the CVSS 4.0 rating of 9.2 with AC:H and AT:P, and in the assessed CVSS 3.1 vector AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H). The vendor addressed the flaw in OpenBao v2.6.0; no public exploit identified at time of analysis.
Arbitrary code execution in GNU Emacs 28.1 through 31.1 is triggered simply by opening a crafted file: an untrusted read-symbol-shorthands value supplied by that file reaches the Lisp reader's intern and unintern functions and is honored under Emacs's default configuration, so no special user settings or opt-ins are required. Exploitation is bounded by delivery - the attacker must get a victim to open the malicious file locally (AV:L with UI:R), and any resulting code executes with the privileges of the user running Emacs; no network service, listener, or authentication is involved. The issue carries a CVSS 4.0 score of 7.5 and is assessed under CVSS 3.1 as AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, with high confidentiality, integrity, and availability impact and no public exploit identified at time of analysis.
Local cross-user code execution with privilege-escalation potential affects the Windows builds of GNU wget distributed by eternallybored.org (releases 0 through 1.21.4 inclusive). The flaw is a hardcoded configuration location, C:\msys64, that unprivileged users can write to: a low-privileged local attacker who plants a wgetrc there can abuse the use_askpass directive so that arbitrary code is executed in the security context of a higher-privileged user who later runs the affected wget build. The attack is not remotely reachable and does not trigger on its own, which is captured by the UI:R component of the CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 7.8), and no public exploit code was identified at time of analysis.
Local privilege escalation to root in Netdata versions prior to 2.10.4: the setuid-root ndsudo helper command fail2ban-client-status-socket accepted a caller-supplied --socket_path argument from the low-privileged netdata service account, letting that account point root's fail2ban-client at an attacker-controlled UNIX socket. Because fail2ban-client's CSocket.receive() deserializes the socket response with pickle.loads(), a crafted reply yields attacker-controlled code execution as root on any host where fail2ban-client is installed and the setuid ndsudo helper is present (default in affected packaged builds). The vector is strictly local (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H), so a prior foothold as the netdata account is mandatory, and hosts without fail2ban-client are not exploitable through this path; no public exploit code has been identified at time of analysis.
Memory exhaustion in Netdata versions prior to 2.11.0 allows a remote, unauthenticated attacker to inflate small, highly compressed WebSocket frames into large server-side allocations and, by repeating this across concurrent connections, drive the monitoring process to memory exhaustion and termination. The weakness sits in the unauthenticated WebSocket server's permessage-deflate handling, which is negotiated before authentication, so exploitation requires only network reachability to the default web listener (0.0.0.0:19999) - instances bound to localhost or shielded by firewalls are not reachable. Vendor-released patch: 2.11.0, which introduces a compressed-to-decompressed ratio cap; no public exploit code identified at time of analysis and no CISA KEV entry, but the independent assessment rates this a legitimate availability risk given the trivial trigger and the CVSS 3.1 score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).
Remote, unauthenticated denial of service against applications running FasterXML jackson-core 2.17.0 through 2.18.10: a JSON string of attacker-supplied numeric-looking text coerced into a BigDecimal, BigInteger, Double, or Float target drives NumberInput.looksLikeValidNumber() into quadratic regular-expression backtracking, and a single 160,000-character value was measured at roughly 74 seconds, so a small number of concurrent requests of ordinary body size can exhaust a server's request-handling thread pool. Reachability is narrowed by the data-binding requirement: only endpoints where jackson-databind's StdDeserializer/NumberDeserializers perform String-to-number coercion are exposed, and 2.16.x and earlier do not contain the affected method at all. No public exploit code identified at time of analysis, and no CISA KEV confirmation of active exploitation.
Unauthenticated remote code execution in SGLang 0.5.11 through 0.5.14 occurs when the multimodal generation runtime is launched in disaggregated-diffusion mode, where the DiffusionServer orchestrator binds a ZeroMQ ROUTER socket to a network-reachable interface with no authentication and passes the final frame of every received multipart message directly into pickle.loads() before any validation is performed. Rated CVSS 3.1 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), the flaw lets any remote party that can deliver a multipart ZMQ message to that socket execute arbitrary Python code in the serving process, yielding full compromise of confidentiality, integrity and availability on the host. No public exploit identified at time of analysis; exploitation requires the exposed orchestrator socket to be reachable beyond localhost, so loopback-bound or single-node deployments are not remotely exploitable.
Integer overflow in libstdc++ within Red Hat Hardened Images can cause undersized memory allocations, leading to memory corruption or application instability when a consuming application passes an attacker-controllable large size to the C++ new or new[] operator. Exploitation requires a specific application input path that triggers CWE-190 and an exploitable heap layout, as reflected in the High severity (CVSS 7.7, AC:H) assigned by Red Hat; the flaw is not exploitable against libstdc++ in isolation. No public exploit code, proof-of-concept, or CISA KEV listing is identified in the available data.
Denial of service in Erlang/OTP's ASN.1 OBJECT IDENTIFIER decoders allows a remote, unauthenticated attacker to stall TLS-processing services by sending a crafted certificate during the handshake. Erlang/OTP releases from OTP 17.0 up to the fixed versions OTP 27.3.4.18, OTP 28.5.0.7 and OTP 29.1.1 are affected whenever the service parses a peer's X.509 certificate - the default for TLS clients (which always parse the server certificate) and for mutual-TLS servers - because the vulnerable BER OID decoder runs before signature and trust-chain verification, so an untrusted self-signed certificate is sufficient to trigger it. A single crafted OID with one very large arc (roughly 262 KB of continuation bytes) burns about 13 seconds of CPU, so sustained denial of service requires repeated connections; no public exploit code identified at time of analysis, and the impact is availability only (vendor CVSS 8.2; independently assessed as CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).
Authenticated remote attackers can exhaust node memory on Erlang/OTP SSH daemons by repeatedly opening "session" channels that never receive a shell, exec, or subsystem handler, eventually driving the BEAM emulator out of memory and terminating it - which kills every application sharing that node, not just the SSH service. The flaw (CWE-770) affects OTP 17.0 through 27.3.4.18, 28.5.0.7, and 29.1.1 (ssh 3.0.1 through 5.2.11.13, 5.5.2.6, and 6.0.6); an attacker must be able to complete SSH authentication first, but no user interaction, special configuration, or valid file/credential access is required, and CVSS scores it 7.1 (CVSS 4.0 availability-high, PR:L). No public exploit identified at time of analysis, and vendor-released patches are available. The documented max_channels daemon option does not mitigate the attack, so operators cannot rely on it as a stopgap.
Erlang/OTP's ssl application in affected releases (OTP 22.2 through the fixed 27.3.4.18, 28.5.0.7 and 29.1.1) will complete a TLS 1.3 client handshake against any peer that answers with an unsolicited pre_shared_key extension, allowing that peer to impersonate the intended server while holding no certificate, no private key and no prior session. Because the bogus resumption flag short-circuits certificate handling, ssl:connect returns {ok, Socket} even though certificate path validation, verify_fun, hostname verification, partial_chain, CRL checking and OCSP stapling are all skipped; an unauthenticated network-positioned attacker (man-in-the-middle, hijacked route/DNS, or a server the client is lured into contacting) can exploit this, and clients restricted to TLS 1.2 are not affected. A vendor patch is available and no public exploit code has been identified at time of analysis.
Heap-based buffer overflow in libslirp's DHCPv6 and TFTP reply builders lets a malicious guest write attacker-controlled content and length past the end of the host-side reply buffer, causing host process crashes (denial of service) and potentially arbitrary code execution in the host. The flaw only manifests when the host interface is configured with a small, non-default MTU - the default MTU is explicitly unaffected - and requires the guest to reach libslirp's built-in DHCPv6 or TFTP service, which makes this a guest-to-host escape surface for QEMU user networking and slirp4netns rootless containers. Red Hat Enterprise Linux 8, 9 and 10 and OpenShift Container Platform 4 ship affected builds; no public exploit code and no confirmed active exploitation were identified at time of analysis, and the assessed vector is unauthenticated (PR:N) but high complexity (AC:H) because of the configuration prerequisite.
Unauthenticated path traversal in the Dancer2 Perl web framework (versions 2.1.0 up to but not including 2.2.0) lets a remote attacker read arbitrary files that the worker process can access, including configuration files such as config.yml stored above public_dir. The flaw only manifests in a non-default deployment where the application names File in its route_handlers configuration and sets static_handler to 0 - because the default static handler refuses dot segments before the File route executes; applications left at defaults are not affected. The vendor has released Dancer2 2.2.0 with a containment fix, EPSS is low (0.19%, 8th percentile), and no public exploit code or confirmed active exploitation was identified at time of analysis.
Security-control bypass in the Dancer2 Perl web framework (2.0.0 through 2.1.x) lets a refused route execute anyway: when an application enforces an authorization or security check by having a 'before' hook die and also registers an on_hook_exception handler that halts the response, the post-exception cleanup still runs and destroys the request, response and session the dispatcher needs, so the route body the hook meant to refuse runs and its writes land. The flaw requires that specific non-default application design - apps that do not refuse via dying hooks, or whose exception handler does not halt the response, are not affected - and, when the pattern is present, a single unauthenticated remote request is enough to trigger it (AV:N/AC:L/PR:N/UI:N), giving a high integrity impact on denial-protected state changes. EPSS is 0.17% (7th percentile) and there is no public exploit identified at time of analysis; CISA's SSVC rates exploitation as none, automatable as yes, technical impact partial. Vendor-released patch: Dancer2 2.2.0, which adds a halt check to the cleanup guard and makes hook compilation idempotent.
Denial of service in YARA 4.5.8 occurs when libyara deserializes a crafted compiled rule file (.yrc): malformed external-variable pointers or an out-of-range type field are not validated in the yr_rules_load/yr_rules_from_arena path, resulting in an invalid free in yr_rules_destroy() or a wild pointer dereference in yr_object_create(). Only deployments that load compiled rules from untrusted or third-party sources are exposed, since the assessed vector requires a user or process to actively load the file (UI:R) and no authentication (PR:N); the realistic outcome is a process crash rather than code execution (C:N/I:N/A:H). No public exploit code has been identified at time of analysis, EPSS is low at 0.21% (11th percentile), and the issue is not confirmed actively exploited (CISA KEV).
GPU memory exhaustion in vLLM through 0.29.0 allows remote, unauthenticated attackers to permanently leak GPU KV cache blocks by submitting completion requests containing multiple prompts whose concurrent child requests share a single Mooncake transfer ID. The leak is only reachable in prefill/decode (P/D) disaggregated deployments that have the Mooncake KV-transfer connector enabled - a non-default topology in which the vulnerable ownership bookkeeping runs - and orphaned blocks are never reclaimed until the vLLM process is restarted, progressively starving legitimate inference requests of GPU memory. No public exploit code has been identified at time of analysis and the flaw is not listed in CISA KEV, though the attack is network-reachable, low-complexity, and requires no authentication or user interaction (CVSS 4.0 8.7; independent assessment scores the availability-only impact as CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).
Memory exhaustion in vLLM through 0.29.0 lets remote, unauthenticated attackers crash the inference service by supplying an arbitrary 'tp_size' value inside the 'kv_transfer_params' field of requests to the OpenAI-compatible completion endpoints. Because kv_transfer_params is honored only when the server runs in a prefill/decode (P/D) disaggregated deployment using the NIXL KV-transfer connector, the attacker causes unbounded memory allocation in the decode worker that ends in a kernel OOM-kill and full loss of service availability; confidentiality and integrity are unaffected. No public exploit code was identified at time of analysis and there is no CISA KEV listing, but the flaw is trivially reachable over the network (CVSS 4.0 8.7, AV:N/AC:L/PR:N/UI:N/VA:H), and an upstream fix exists as pull request 51137.
Denial of service in vLLM through 0.29.0 lets unauthenticated remote attackers crash the EngineCore and halt all inference by feeding arbitrary remote host and port values through kv_transfer_params when the P2P secondary KV-offload tier is enabled. Each bogus peer address causes the server to allocate a ZeroMQ socket for an unreachable peer session; because no limit is enforced on concurrent sessions, the sockets accumulate until the context quota is exhausted and an uncaught ZMQError terminates the engine (CWE-770, unlimited resource allocation). Exploitation is gated on a non-default configuration - OffloadingConnector configured with TieringOffloadingSpec plus a p2p secondary tier - and availability is the only affected property; an upstream fix exists in pull request 51504, but no public exploit code has been identified at time of analysis.
Denial of service in vLLM through 0.29.0 allows an unauthenticated remote attacker to crash the NIXL decode worker by submitting a single OpenAI-compatible completion request containing multiple prompts of differing lengths together with kv_transfer_params. The crash occurs in NixlBaseConnectorWorker._apply_prefix_caching, where block-count mismatches between the decode and prefill sides hit a reachable assertion (CWE-617); the decode worker terminates and stays unavailable until manually restarted, so a low-effort request loop can repeatedly take serving capacity offline. Impact is confined to availability (CVSS 4.0 8.7, AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H), with no confidentiality or integrity effect, and exploitation is gated on a non-default prefill/decode DISAGGREGATED topology that uses the NIXL KV-transfer connector - standard single-node vLLM serving is not affected. No publicly available exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, though the trigger is a trivially crafted multi-prompt API call.
Denial of service in vLLM through 0.29.0 allows an unauthenticated remote attacker to crash the decode engine by sending a single inference request whose kv_transfer_params dictionary is incomplete, for example containing only {"do_remote_prefill": true} without the required remote_block_ids, remote_engine_id, remote_request_id, remote_host, and remote_port fields. The malformed metadata raises an uncaught KeyError inside EngineCore scheduling (CWE-248) during add_new_req_to_recv, terminating the decode engine and causing every subsequently routed request to fail until an operator manually restarts it, yielding a vendor CVSS 4.0 score of 8.7 (VA:H, C/I both N). Exposure is limited to deployments running prefill/decode disaggregated mode with the NIXL connector, which is a non-default serving configuration; standard single-node vLLM never processes kv_transfer_params on this path. No public exploit code and no confirmed active exploitation were identified at time of analysis, though the upstream fix and regression tests are public in PR #54807.
Path-based RBAC authorization bypass in Envoy Proxy lets an unauthenticated remote client reach protected backends such as /admin by appending a semicolon path parameter (e.g. /admin;x), because the router strips that suffix before route matching while the RBAC url_path matcher evaluates the untouched raw path. Exploitation is tightly gated rather than default: it requires a route configured with ignore_path_parameters_in_path_matching, a path-based RBAC rule (PathMatcher or UriTemplateMatcher) guarding the protected path, and a crafted request that still selects the protected route after stripping. All releases prior to 1.36.10, 1.37.6, 1.38.4, and 1.39.1 are affected; the vendor has published fixed releases, and no public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis.
Stored cross-site scripting in Envoy Proxy's admin statistics page lets an attacker run script in the admin interface's origin: the /stats?format=html endpoint (StatsHtmlRender) sanitizes statistic values but emits statistic names raw, so a data-plane component that folds attacker-supplied request path segments into dynamic stat names - notably grpc_stats with stats_for_all_methods enabled - can persist a script-bearing name that fires when an operator opens the page in a browser. Every release before 1.36.10, 1.37.6, 1.38.4, and 1.39.1 is affected; the independently assessed vector is CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N (7.4), i.e. unauthenticated remote influence over the injected text but multiple gating prerequisites plus required operator interaction, with impact scoped to the admin origin where privileged same-origin requests can then be issued. No public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV; exploitation is realistic only where the admin HTML endpoint is browser-reachable and a dynamic-stat-generating component is enabled.
Envoy Proxy releases prior to 1.36.10, 1.37.6, 1.38.4, and 1.39.1 can be crashed by a remote, unauthenticated attacker through its HTTP/3 datagram and Capsule Protocol handling (prerequisites: PR:N, no user interaction). When a request enters a stream-recreation path such as an internal redirect, the HttpDatagramHandler keeps a cached pointer to the original RequestDecoder; a subsequent HTTP/3 datagram invokes decodeData through that freed decoder, producing invalid virtual dispatch and process termination (CWE-416 use-after-free, CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H). Exploitation is gated on a non-default configuration - HTTP/3 (QUIC) downstream plus Capsule Protocol enabled, e.g. MASQUE connect-udp tunneling - combined with an internal-redirect route and precise frame sequencing; no public exploit code or CISA KEV entry was identified at time of analysis.
Unauthenticated remote attackers can exhaust memory and trigger an out-of-memory kill of Envoy Proxy by sending HTTP/2 requests that include a large Host header alongside an existing :authority pseudo-header, since the discarded Host value is copied but never charged against header size or count limits, and HPACK dynamic-table indexing lets an attacker repeatedly reference that large value across a bounded number of streams. All Envoy releases before 1.36.10, 1.37.6, 1.38.4, and 1.39.1 are affected, including both the nghttp2 and oghttp2 HTTP/2 codec implementations, and the flaw is reachable on any listener that terminates HTTP/2 with no authentication or user interaction required (CVSS 3.1 base 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, CWE-401). No public exploit code and no confirmed active exploitation have been identified at time of analysis, but the low complexity and lack of prerequisites make this a practical availability risk for internet-facing edge proxies; note the supplied "Authentication Bypass" tag is misleading - the impact is availability-only, with no confidentiality or integrity loss.
Unauthenticated remote clients can crash Envoy Proxy by sending a path-less CONNECT request when the ext_authz HTTP filter is configured to apply query_parameters_to_set or query_parameters_to_remove mutations and the external authorization service returns such a mutation. The crash is a null-pointer dereference in the ext_authz filter's Filter::onComplete path, producing a denial of service (CVSS 7.5, A:H) against the affected proxy process; impact is limited to availability, with no confidentiality or integrity loss. Exploitation is gated by two non-default configuration prerequisites - accepting path-less CONNECT and enabling ext_authz query-parameter mutation - and no public exploit code has been identified at time of analysis.
Denial of service in Envoy Proxy releases prior to 1.36.10, 1.37.6, 1.38.4, and 1.39.1, where the optional oghttp2 upstream HTTP/2 codec accepts a response trailer HEADERS frame that lacks the END_STREAM flag, causing Envoy to complete and deferred-delete the ActiveRequest while oghttp2 keeps the stream open. The resulting dangling reference in ClientStreamImpl (response_decoder_) can be dereferenced by a subsequent frame on that stream, freeing-then-using memory and crashing the Envoy process (CWE-20, CVSS 3.1 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - assessed independently at AC:H). Exploitation is remote and unauthenticated once preconditions hold, but it is limited to non-default configurations: the oghttp2 upstream codec must be explicitly enabled, the malformed trailers must be emitted by the upstream server Envoy proxies to (an attacker-controlled or compromised upstream, or injected frames on that connection), and the default nghttp2 codec rejects the malformed trailers outright. Vendor patches are available (1.36.10, 1.37.6, 1.38.4, 1.39.1); no public exploit code was identified and the issue is not in CISA KEV at time of analysis.
An access-control bypass in Envoy Proxy (all versions prior to 1.36.10, 1.37.6, 1.38.4, and 1.39.1) allows unauthenticated remote clients to reach routes that HTTP RBAC policies were configured to deny, resulting in disclosure of protected content. The flaw only materializes when a NEGATIVE (DENY) policy uses a safe_regex matcher against header values and a byte-oriented route matcher independently reads the raw header bytes; positive ALLOW regexes fail closed and exact, prefix, suffix, and contains matchers are unaffected. No public exploit code has been identified at time of analysis, and the vendor has released fixed versions, so real-world risk is driven almost entirely by whether a deployment uses that specific safe_regex-in-negative-policy configuration.
Request smuggling in Envoy Proxy allows an unauthenticated HTTP/2 client to embed a complete HTTP/1.1 request inside the data payload of an extended CONNECT (a generic, non-WebSocket HTTP upgrade) so that Envoy forwards that payload upstream before the upstream has accepted the upgrade, writes it unframed to a keep-alive HTTP/1.1 upstream, and returns the upstream socket to the shared pool with a smuggled response still queued - meaning a different, unrelated downstream client can subsequently be served the attacker's response. Every Envoy release prior to 1.36.10, 1.37.6, 1.38.4, and 1.39.1 is affected, but exploitation is configuration-dependent: the listener must proxy a generic non-WebSocket upgrade to an HTTP/1.1 upstream with backend keep-alive enabled, shared (non-per-downstream) connection pools, and max_requests_per_connection not set to 1; WebSocket upgrades, plain CONNECT, disabled backend keep-alive, per-downstream pools, and max_requests_per_connection=1 are explicitly out of scope for the demonstrated path. No public exploit code has been identified at time of analysis, and this CVE is not listed in CISA KEV.
Arbitrary command injection on Windows in the Perl distribution Email::Sender (Email::Sender::Transport::Sendmail versions before 2.602) lets an attacker who controls a From, To, or Cc header address execute commands as the sending process, because on MSWin32 the envelope sender and recipients are concatenated into a single command string that Perl's open() hands to a shell. The flaw is strictly Windows-only: on every other platform the transport uses open()'s list form and passes arguments directly to sendmail with no shell involved, so the injection path does not exist there, and exploitation additionally requires that the application use the sendmail transport rather than the SMTP transport and that the caller supply no explicit envelope (letting Email::Sender::Simple derive addresses from headers). The vendor CVSS of 9.8 (AV:N/AC:L/PR:N/UI:N) overstates real-world risk given that hard platform gate; our assessment uses CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, EPSS is low at 0.22% (13th percentile), SSVC records no observed exploitation with automatable attack and total technical impact, and no public exploit code was identified at time of analysis, though a vendor patch (2.602) and an upstream commit are public.
OpenBao versions prior to 2.6.0 fail to reject syntax-significant characters when templated identity data is substituted into ACL, PKI, and SSH policies, allowing an authenticated principal who can write that identity data to broaden path matching, obtain certificates for unauthorized domains, or add unauthorized SSH principals. Exploitation is gated on a non-default configuration: the policy must use templates that substitute attacker-modifiable identity metadata (for example {{identity.entity.metadata.domains}} or {{identity.entity.metadata.sans}}), and the attacker must already hold the capability to update that identity record (such as update on identity/entity), consistent with the assessed CVSS 3.1 vector AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N. Deployments whose templates rely solely on the randomly generated identity.entity.id value are not affected, there is no user interaction, and no public exploit code was identified at time of analysis.
Local privilege escalation in BleachBit on Windows lets an unprivileged local user turn an elevated cleaning operation into arbitrary privileged file deletion and, via Windows Installer rollback behavior, full SYSTEM privileges. The flaw affects BleachBit versions prior to 6.0.1 and is exploitable by an authenticated, unprivileged interactive user who wins a TOCTOU race while BleachBit runs with elevated rights in privileged Windows cleaning mode; the vector is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (7.8). No public exploit code was identified and there is no CISA KEV listing at time of analysis, so the practical risk is a genuine local privilege-escalation issue worth prioritizing on Windows hosts that run BleachBit with elevation.
An authorization flaw in the pki-core v2 REST ACL filter lets an authenticated member of the default Certificate Manager Agents group invoke profile-management operations reserved for Administrator-level accounts, so a request to POST /v2/profiles/raw that should require profiles.create is instead authorized under the lower-privileged profiles.approve permission. The root cause is that when a literal ACL key (profiles.create) and a wildcard ACL key (profiles.approve) both match, the filter picks the winner by lexicographic string comparison rather than by specificity, allowing the wildcard mapping to override the more specific literal one; CVSS 3.1 rates this 8.1 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N), with the highest threat to the confidentiality and integrity of the CA's issuance policy. Exploitation requires valid agent-level credentials and the default ACL configuration, and no public exploit code has been identified at time of analysis, so this is a privilege escalation inside an existing trusted role rather than unauthenticated access.
Heap-based buffer overflow in X.Org libXrender before 0.9.13 allows a malicious or compromised X server to inject and execute arbitrary code in attached X11 clients via a crafted response to the RenderQueryPictFormats request. This is a reverse-direction attack where the victim must actively connect a vulnerable X11 client (linked against libXrender < 0.9.13) to an attacker-controlled or hijacked X server - typical exposure is via SSH X11 forwarding to an untrusted host or a remote DISPLAY connection; local trusted X servers are not affected. No public exploit code has been identified at time of analysis, and exploitation is non-trivial (AC:H) with no attacker authentication required (PR:N), but an upstream fix is available and the CVE description identifies 0.9.13 as the fixed version boundary.
Heap-based buffer overflow in libX11 before 1.8.14 allows a malicious or compromised X server to corrupt memory in connecting X11 clients via a crafted XkbGetMap reply that overflows the key_sym_map. This client-side vulnerability has an inverted threat model: the attacker must control the X server the victim connects to, with exploitation requiring user interaction (UI:R) and high attack complexity (AC:H). CVSS 3.1 score is 7.5 High; no public exploit code has been identified at time of analysis.
Elevated-privilege container restoration in CRI-O 1.34 and later, including downstream Red Hat OpenShift Container Platform 4.17+, lets an authenticated Kubernetes user who can create a pod from a crafted checkpoint image bypass the destination pod's security context. The restored process keeps credentials, Linux capabilities, no_new_privs and seccomp state stored in the checkpoint instead of the destination configuration, allowing execution across the container security boundary. Exploitation requires non-default checkpoint/restore (CRIU) support to be enabled and RBAC permission to create pods from malicious checkpoints; no public exploit code is identified and no vendor-released fix is available at time of analysis, so the vendor CVSS 3.1 score of 8.8 overstates urgency given those prerequisites (our assessment raises attack complexity to High).
Arbitrary code execution in the npm front-matter parser gray-matter is reachable through its built-in JavaScript engine, which evaluates front matter with eval() whenever the document declares a js/javascript language fence. Any application that passes attacker-influenced markdown or front-matter text into gray-matter's parse call can be induced to run attacker-supplied JavaScript in the Node.js process - the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, 9.8) rates this as unauthenticated remote code execution, with the practical caveat from our assessment that the attack surface is gated by whether the host application exposes gray-matter parsing to untrusted content. Affected coverage is broad rather than version-specific: the reporter states all versions are impacted and verified 4.0.3, while there is no CISA KEV entry, no confirmed public exploit code, and a low EPSS of 0.17% (7th percentile) indicating limited observed exploitation pressure at time of analysis.
Command injection in CrossWire Xiphos 4.3.2 and earlier lets a local attacker execute arbitrary shell commands with the privileges of the user running the application by placing shell metacharacters in data that Xiphos later interpolates into unsanitized popen() shell pipelines. Two code paths are involved: the personal-commentary rename action (on_rename_perscomm_activate in src/gtk/menu_popup.c), where the module section name is spliced into a cd/sed command, and the separate-image viewer (show_separate_image in src/main/url.cc), where an image filename is spliced into an external viewer's command line. Exploitation requires the victim to trigger one of those actions on attacker-supplied data (a crafted module or image file), the impact is confined to the victim's own account because no privilege escalation is demonstrated, and publicly available exploit code exists (SSVC records exploitation as 'poc'), although the issue is not in CISA KEV and EPSS is low at 0.15% (5th percentile).
Use-after-free in Suricata before 8.0.7 can crash the HTTP/2 inspection engine when a transaction is inspected by rules that use http.response_header both with and without a transform. The flaw is remotely triggerable by HTTP/2 server responses traversing the sensor, requires no authentication per the CVSS vector, and the vendor has released 8.0.7 as the fix. No public exploit code or confirmed active exploitation was identified at time of analysis; the assessed impact is primarily denial of service and limited memory disclosure, not confirmed code execution, and exploitation depends on the specific dual-rule HTTP/2 configuration.
Suricata 8.x before 8.0.7 contains a type confusion vulnerability in the DoH2 (DNS over HTTPS version 2) parser that can result in an invalid free, leading to memory corruption. An unauthenticated remote attacker can trigger this by sending a crafted DoH2 request that performs an HTTP1-to-HTTP2 upgrade through a monitored network, potentially causing a crash or arbitrary code execution. The vulnerability is exploitable by default in 8.x sensors because the doh2 app-layer protocol is enabled out-of-the-box; no public exploit code has been identified at time of analysis, but the severity is high.
Remote code execution in Mistral Vibe before 2.25.5 allows an attacker to run arbitrary shell commands with the privileges of the user running the tool, because worktree creation executes a repository's own git hooks - notably the post-checkout hook and the fsmonitor command - before any workspace trust validation takes place. The attack requires the victim to deliberately open, clone, or check out an attacker-controlled repository (user interaction is mandatory, and the request itself is unauthenticated per the CVSS PR:N vector), and code execution is bounded by the permissions of the Vibe user, with no privilege escalation or server-side attack surface. There is no public exploit identified at time of analysis and the flaw is not confirmed as actively exploited; a vendor-released patch in 2.25.5 addresses the ordering bug.
Malformed UTF-16 decoding in libexpat through 2.8.4 lets remote attackers hide XML markup from the parser: a lone high surrogate paired with the following code unit is accepted as a valid surrogate pair, so a character such as '<' is consumed as part of the pair and never tokenized. Only applications that parse UTF-16-encoded XML (little- or big-endian) from an untrusted source are affected - the dominant UTF-8 input path is not exploitable - and meaningful integrity impact additionally requires a downstream filter, sanitizer, or validator that trusts the parsed structure and therefore sees different markup than Expat exposes. No public exploit has been identified at time of analysis; an upstream fix is available in the Expat repository (PR #1282, commit ff6e1d7e750bbe245178f51a47a965dc8342861a), reported via VulnCheck.
Information disclosure in Exim before 4.100.1 allows attackers who control or can impersonate a proxy in the configured proxy_protocol_hosts set to read uninitialized stack memory when PROXY Protocol is enabled, but only in non-default deployments and with limited confidentiality impact. This is a conditional flaw requiring attacker control of a trusted proxy; stock Exim installations without Proxy-Protocol are unaffected. No public exploit code or evidence of active exploitation was identified at time of analysis.
Serialization of Node.js Buffer objects in the JavaScript library devalue 5.1.0 through 5.9.2 leaks unrelated process memory: when stringify, stringifyAsync, or uneval encounters a Buffer, it emits the view's entire backing ArrayBuffer instead of only the visible bytes, and because small Buffers are carved from Node's process-wide shared allocation pool, the serialized output can include up to roughly 64 KB of memory belonging to other in-flight requests. Any server-side-rendered application that serializes a Buffer into HTML without authentication - a SvelteKit or Nuxt page whose load() returns a small Buffer or reads a small file - can therefore publish another user's request body or Authorization header in a public response, and the flaw triggers on every such render because it occurs during serialization rather than parsing, so the library's parse/unflatten prototype-pollution and denial-of-service guards provide no protection. Unauthenticated remote attackers need no user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, 7.5), the affected CPE is cpe:2.3:a:sveltejs:devalue:*, and no public exploit code or confirmed active exploitation was identified at time of analysis.
Memory-exhaustion denial of service in SGLang through 0.5.20 allows anyone who can reach the decode engine's internal ZMQ rank port to terminate the serving process by sending a single STAGING_REQ frame carrying an extremely large chunk_idx value. The flaw applies only to deployments running prefill/decode disaggregation - a non-default, multi-engine serving topology - and requires network reachability to the inter-rank ZMQ port that normally carries unauthenticated traffic on a trusted cluster network; when that port is bound to loopback or an isolated back-end network, the issue is not reachably exploitable. No public exploit identified at time of analysis, and the impact is confined to availability: the scheduler allocates memory until the system runs out and the process is killed, with no data exposure or code execution.
Remote denial of service in osmo-iuh's HNBGW (Home NodeB Gateway) lets a network-reachable peer on the Iuh interface crash the process by sending a RANAP connection-oriented direct-transfer message carrying an arbitrarily sized NAS-PDU, which trips a reachable assertion in ranap_handle_co_dt(). Per the CVE description the affected range is osmo-iuh 1.10.0 through 1.14.5, although the ENISA EUVD entry lists a much narrower 0.1.0 <1.8.0 scope and the supplied CPE points at osmocom:osmo-bsc, so the exact affected version set should be confirmed against the vendor advisory. Impact is availability-only (CVSS 3.1 base 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H; SSVC Technical Impact: partial) with no confidentiality or integrity loss; there is no CISA KEV listing, no public exploit code identified at time of analysis, and EPSS is low at 0.17% (7th percentile).
Remote denial of service in Osmocom osmo-bsc 1.0.1 through 1.14.1: a heap-based buffer overflow in ipaccess_proxy_read_msg() is triggered when a crafted IPA frame carries an attacker-controlled length value that is used without adequate validation against the actual buffer size. The issue is remotely reachable and requires no authentication or user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N) from any host able to talk to an osmo-bsc instance with the ipaccess proxy component deployed, and the assessed impact is availability-only (C:N/I:N/A:H), meaning a successful trigger corrupts heap memory and crashes the process. There is no public exploit identified at time of analysis and EPSS is a low 0.14% (4th percentile), consistent with the deployment reality that BSC signaling paths such as the IPA/A-bis proxy are normally confined to segmented, non-public operator networks.
Prototype pollution in the deepmerge JavaScript library (all versions through 4.3.1) allows an attacker who controls a source object passed into a merge operation to inject properties such as '__proto__', 'constructor', or 'prototype' into the resulting object's prototype chain. The impact is latency-dependent: applications that merge untrusted data (for example, a JSON request body) and then read properties without own-property checks will silently inherit attacker-chosen values, which can corrupt application logic, bypass authorization checks, or influence downstream behaviour. The flaw is a library primitive rather than a standalone exploit, and no public exploit code was identified at time of analysis; the vendor CVSS 4.0 score of 8.7 reflects integrity impact only (VC:N/VA:N), and an independent assessment rates it considerably lower (CVSS 3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N) because exploitation requires the consuming application to both pass attacker-controlled source objects and perform unchecked inherited-property reads.
Denial of service in the CSSOM JavaScript library through 0.5.0 allows unauthenticated remote attackers to terminate a parsing process by supplying a stylesheet declaration named 'length', a reserved property name that is not validated and therefore overwrites the internal declaration counter; the corrupted counter then drives an oversized memory allocation when cssText is serialized, crashing the process. Exploitation is conditional rather than automatic: the host application must feed attacker-controlled CSS into CSSStyleDeclaration.setProperty() or stylesheet parsing and must later serialize that declaration via cssText, so deployments that only parse trusted first-party CSS, or that never serialize untrusted input, are not exposed. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV; the provided CVSS 4.0 score of 8.7 (assessed as CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) reflects a high availability-only impact with no confidentiality or integrity effect, and the library itself is not network-exposed.
Cross-client information disclosure in http-cache-semantics through 4.2.0 allows remote, unauthenticated attackers to receive cached responses that were generated for other users. The library's _varyMatches() function performs byte-for-byte comparison of Vary header values and therefore fails to treat a wildcard 'Vary: *' directive as a prohibition on shared-cache reuse, so a request for a URL previously fetched by someone else can be satisfied from cache with that other client's sensitive per-user data. Exploitation is conditional and non-deterministic - it requires a shared, multi-user cache deployment and an origin that emits wildcard Vary on cacheable responses - which is consistent with the vendor CVSS 4.0 score of 8.2 with AC:H and AT:P; no public exploit code has been identified at time of analysis.
Denial of service in source-map-js up to and including 1.2.1 allows an attacker who can supply an indexed source map to hang the Node.js process: the library reads the per-section offset.line value without bounds checking, so an arbitrarily large integer forces a long synchronous loop that blocks the event loop and starves all other requests. The flaw (CWE-1284, improper validation of a specified quantity) is reachable only where a service actually parses attacker-controlled maps - for example an online transpiler, upload-accepting bundler service, or error/stack-trace resolver - since source maps are normally trusted build-time artifacts; the assessed CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H) reflects that data-flow prerequisite, and no public exploit was identified at time of analysis. Impact is availability only; despite the 'Information Disclosure' tag in some feeds, there is no confidentiality or integrity loss in the assessed vector.
TLS certificate validation bypass in AnyIO (pip/anyio) versions before 4.14.2 lets an attacker who already holds an on-path man-in-the-middle position impersonate a server named with a non-ASCII internationalized domain name. AnyIO's TLSStream.wrap() encoded the target host name with IDNA 2003 (via the Python standard library) instead of IDNA 2008 before matching it against the peer certificate, so a host like 'faß.de' was compared against the certificate for 'fass.de' - an attacker can obtain a legitimately CA-issued certificate for that wrong domain and have it validate on the client. Exploitation requires all three of: an application calling connect_tcp(tls=True) or TLSStream.wrap() with an affected unicode host name, a pre-existing connection hijack/redirect the vulnerability does not itself provide, and attacker acquisition of a valid certificate for the IDNA 2003-encoded name; ASCII-only host names are unaffected. No public exploit code has been identified at time of analysis, and patched version 4.14.2 is available.