Suse
Monthly
Sandbox escape and out-of-sandbox arbitrary code execution in Google Chrome (desktop) before 152.0.7977.75, rooted in an incorrect authorization flaw in the FileSystem component. A remote attacker who lures a victim into opening a crafted HTML page can break out of the renderer sandbox and run code with the privileges of the browser process. Rated High by Chromium and CVSS 9.6; the vendor has shipped a stable-channel patch, though no public exploit code or active exploitation has been identified at time of analysis.
Sandbox-escaping remote code execution in Google Chrome for Android before 152.0.7977.75 stems from a use-after-free in the Shared Tab Groups feature (CWE-416). A remote attacker who lures a victim into visiting a crafted HTML page can corrupt freed memory to execute arbitrary code outside the renderer sandbox. Chromium rates the severity Critical (CVSS 9.6); the vendor has shipped a fix, but no public exploit has been identified at time of analysis.
Sandbox-escaping remote code execution in Google Chrome for Android before 152.0.7977.75 stems from a use-after-free in the WebGL implementation, letting a remote attacker who lures a victim to a crafted HTML page execute arbitrary code OUTSIDE the renderer sandbox. Rated Critical by Chromium with a CVSS 9.6 (scope-changed) vector; a vendor patch shipped in the September 2026 Stable channel update. No public exploit identified at time of analysis, though the tracker bug (issues.chromium.org/546260492) and Google's own reporting indicate the flaw is well characterized.
Stack-based buffer overflow in the GPU component of Google Chrome on Windows (prior to 152.0.7977.75) enables full sandbox escape and arbitrary code execution on the host operating system. Exploitation is a two-stage chained attack: an attacker must first compromise the renderer process (via a separate vulnerability or exploit), then leverage this GPU flaw to break out of Chrome's sandbox and execute code with elevated host privileges. Google has released a patch in the stable channel update for desktop; no public exploit code or CISA KEV listing has been identified at time of analysis.
Use-after-free in Chrome's TabStrip component enables remote code execution outside the renderer sandbox in Google Chrome versions prior to 152.0.7977.75. An attacker must social-engineer a user into a specific UI interaction to trigger the memory-corruption primitive, after which arbitrary code executes at browser-process privilege - a full sandbox escape. Google has issued a stable channel patch; no public exploit or CISA KEV listing has been identified at time of analysis.
Use-after-free in Google Chrome's Browser process prior to version 152.0.7977.75 enables sandbox escape, allowing an attacker who has already compromised the renderer process to execute arbitrary code outside the Chrome sandbox via a crafted HTML page. The CVSS vector (AV:N/AC:H/S:C/C:H/I:H/A:H) reflects both the network-reachable delivery and the scope change from renderer to host-level execution. No public exploit or CISA KEV listing has been identified at time of analysis, but sandbox-escape primitives of this class are highly valued in exploit chains.
Remote code execution inside Chrome's sandbox is achievable via a use-after-free in WebRTC, triggered when a victim visits a specially crafted HTML page. Affected versions are all Chrome releases prior to 152.0.7977.75 across desktop platforms. No public exploit code or CISA KEV listing has been identified at time of analysis, though the sandboxed execution boundary limits the practical impact compared to the raw CVSS 8.8 score - Google's own Chromium severity rating of 'Medium' reflects this containment.
Sandbox escape in Google Chrome's TabStrip component (versions prior to 152.0.7977.75) allows a remote attacker who has already achieved renderer process compromise to execute arbitrary code outside the Chrome sandbox via incorrect authorization in tab management IPC. The attack chain requires two conditions to be met simultaneously: a prior renderer exploit and social engineering to deliver a crafted HTML page - placing this firmly in the chained-exploit category despite the high CVSS base score. A vendor-released patch is available in Chrome 152.0.7977.75; no public exploit code or active exploitation has been identified at time of analysis.
Sandbox escape in Google Chrome's Chromoting (Chrome Remote Desktop) component on Windows allows a local attacker to execute arbitrary code outside the Chrome sandbox via a crafted local program, affecting all Chrome for Windows versions prior to 152.0.7977.75. The root cause is incorrect authorization (CWE-863) within the Chromoting subsystem, where flawed authorization logic fails to restrict a local program from interacting with Chromoting in a way that crosses the sandbox boundary. Google has released a patched version (152.0.7977.75), and no public exploit has been identified at time of analysis, though the full post-sandbox C:H/I:H/A:H impact warrants prompt remediation.
Remote code execution in Google Chrome for Android before 152.0.7977.75 stems from a use-after-free in Dawn, Chrome's WebGPU/GPU graphics abstraction layer, and - per Google's advisory - allows a crafted HTML page to execute arbitrary code outside the renderer sandbox. Exploitation only requires an unauthenticated victim to visit a malicious page, giving the attacker high-impact code execution on the device. No public exploit has been identified at time of analysis and the issue is not in CISA KEV, though the sandbox-escape framing makes it a high-priority browser patch.
Remote code execution within the browser sandbox is possible in Google Chrome versions prior to 152.0.7977.75 due to a use-of-uninitialized-resource flaw (CWE-908) in the V8 JavaScript engine. An attacker can trigger the vulnerability by luring a user to a crafted HTML page, with no authentication or special privileges required beyond normal web browsing. Google has released the patched build 152.0.7977.75; SSVC rates exploitation status as none and no CISA KEV listing has been identified at time of analysis.
Access-restriction bypass in Google Chrome desktop prior to 152.0.7977.75 lets a remote attacker who first tricks a user via social engineering leverage a co-installed application to escape Chrome's system access boundaries. The flaw is an improper input validation (CWE-20) issue in the browser's DataTransfer component, rated High by Chromium and fixed in the September 2026 Stable channel. EPSS is low (0.16%, 5th percentile), no public exploit or CISA KEV listing exists, so realistic risk is bounded by the required user interaction and the presence of a malicious co-installed app.
Remote code execution in Google Chrome desktop before 152.0.7977.75 stems from a use-after-free in the Proxy component that a remote attacker can trigger with crafted network traffic to run arbitrary code OUTSIDE the browser sandbox. Google rates the Chromium severity High and a patched Stable channel build is available; no public exploit code has been identified at time of analysis. Because the flaw yields a sandbox escape rather than a contained renderer bug, successful exploitation gives attacker-controlled code on the host at browser-process privilege.
Unbounded recursion in Net::DNS before 1.57 for Perl allows a remote unauthenticated attacker to exhaust memory and terminate any DNS forwarder or proxy process by sending a crafted DNS message carrying a TSIG record misplaced in the answer or authority section with an empty MAC field. Because the library's decoder does not drop the malformed packet as RFC 8945 section 5.2 requires, the TSIG survives the re-encoding strip step and drives `sig_data` into infinite recursion; payloads under 100 bytes on the wire are sufficient to crash the process. No public exploit has been identified at time of analysis, and EPSS indicates low current exploitation probability (0.17%), though the trivially small payload and zero-authentication requirement make this an operational priority for any Perl-based DNS forwarder or proxy deployment.
Thunderbird's remote attachment allowlist control (`mail.allowed_attachment_hostnames`) can be bypassed due to insufficient regex escaping of configured hostname values, allowing attacker-controlled servers to serve remote attachments that the filter was intended to block. Affected are all Thunderbird releases prior to 155 and 153.2; because hostname strings containing dots and other regex metacharacters are interpolated directly into a regular expression without sanitization, a crafted attachment hostname can pattern-match an allowlisted domain without being that domain. No public exploit has been identified at time of analysis, and EPSS sits at 0.15% (4th percentile), consistent with low-urgency real-world exploitation risk.
Heap memory disclosure in Mozilla Thunderbird's IMAP client allows a malicious IMAP server to trigger a use-after-free by sending a crafted ID extension response, leaking heap contents that are subsequently persisted to the user's prefs.js file on disk. All Thunderbird releases prior to 155, 140.15 (ESR), and 153.2 across three active release channels are affected. No public exploit or active exploitation has been identified at time of analysis; the EPSS score of 0.15% (4th percentile) reflects low current exploitation probability.
Thunderbird's mail header parser triggers a one-byte buffer over-read (CWE-126) when processing a maliciously crafted message header, potentially exposing a single byte of adjacent heap memory to the sender. All Thunderbird versions across three active release branches are affected until patched - 155, 140.15, and 153.2. No public exploit has been identified and EPSS sits at the 4th percentile, but the network-accessible attack path with no user interaction required keeps this relevant for unpatched deployments.
Use of uninitialized memory in Mozilla Thunderbird's MIME parser allows a remote attacker who sends a specially crafted email to trigger an error condition in certain MIME bodies, causing the client to read uninitialized memory. Depending on what previously occupied that memory, this can leak sensitive process data or crash the application. The flaw was fixed in Thunderbird 155, 140.15 ESR, and 153.2; no public exploit has been identified and EPSS exploitation probability is low (0.15%, 4th percentile).
Arbitrary code execution in Mozilla Thunderbird before 154 (and before ESR 153.2) on Windows allows a crafted calendar (iCalendar) invitation to attach a file:// URI that points at a local or network-hosted executable, bypassing Thunderbird's normal blocking of executable attachments. When the new invitation display is enabled the attachment can also be shown under a misleading, benign-looking filename. No active exploitation is confirmed (not in CISA KEV) and no public exploit code has been identified; EPSS is low at 0.15% (5th percentile).
The BEAM runtime in Erlang/OTP crashes when a remote attacker sends a crafted packet to any exposed TCP port using the inet driver with {packet,4} framing, exploiting a signed integer overflow in packet length calculation inside packet_parser.c and inet_drv.c. Affected deployments span OTP release lines 17 through 29, with vendor-released patches available (27.3.4.17, 28.5.0.6, and 29.0.6); no active exploitation is confirmed in CISA KEV and no public exploit code has been identified at time of analysis. The vendor explicitly characterizes remote code execution as 'extremely unfeasible,' making denial-of-service via VM crash the realistic worst-case impact.
Erlang/OTP's inets HTTP server (httpd) fails to enforce an administrator-configured request body-size limit when processing chunked transfer-encoded requests, enabling unauthenticated remote attackers to exhaust server memory and cause denial of service. Affected OTP branches span 17.x through 27.3.4.16, 28.x through 28.5.0.5, and 29.x through 29.0.5, covering inets versions 5.10 through 9.7.1. No public exploit code has been identified and the CVE is not listed in the CISA KEV catalog, but the zero-authentication, low-complexity network attack path makes this an operationally straightforward DoS risk for any deployment exposing inets httpd to untrusted clients.
Request smuggling in Erlang OTP inets (versions 17.0 through 29.x) arises when the httpd server sits behind a Content-Length-preferring reverse proxy: inets frames the request body by chunked Transfer-Encoding and silently discards a co-present Content-Length header, while the front-end proxies request boundaries by Content-Length, producing a classic CL.TE desync. An unauthenticated network attacker in this topology can inject a crafted prefix into a subsequent victim's HTTP request, potentially enabling session hijacking, credential theft, or cache poisoning against other users of the same back-end. No public exploit has been identified at time of analysis, the vulnerability is not listed in CISA KEV, and vendor patches are available for the OTP 27.x, 28.x, and 29.x release branches.
Remote unauthenticated attackers can exploit Erlang/OTP's built-in inets HTTP server across OTP versions 22.2 through 29.0 to conduct HTTP Request Smuggling by sending headers with whitespace before the colon - a malformed construct the server silently discarded rather than rejecting as mandated by RFC 7230 Section 3.2.4. When inets is deployed behind a front-end proxy or load balancer that interprets such headers differently, the resulting parsing discordance creates a desynchronized request boundary exploitable for session hijacking, authentication bypass, or cache poisoning. No public exploit has been identified at time of analysis; vendor-released patches are available across all three affected OTP release branches.
Memory safety vulnerabilities across multiple internally discovered bugs in Firefox 154 and Firefox ESR 153.1 allow network-based attackers to potentially achieve full browser compromise through memory corruption (CWE-119). Mozilla's own advisory clusters dozens of individual Bugzilla reports - including buffer overflows and related defects - under a single advisory umbrella, noting that sufficiently motivated attackers could likely exploit some of these bugs. Vendor-released patch is available: Firefox 155 and Firefox ESR 153.2. No public exploit identified at time of analysis.
Memory corruption in Mozilla Firefox 154, Firefox ESR 153.1, and Firefox ESR 140.14 stems from a batch of internally discovered memory-safety defects that Mozilla presumes could be exploited to run arbitrary code within the browser process. The flaws were found by Mozilla's own developers and fuzzing efforts (no external report), affect the mainline and both ESR trains, and are resolved in Firefox 155, ESR 140.15, and ESR 153.2. There is no public exploit identified at time of analysis and EPSS exploitation probability is low (0.17%, 6th percentile).
Memory-corruption defects in Mozilla Firefox 154 were discovered internally by Mozilla and bundled under CVE-2026-84142 (advisories MFSA2026-82 and MFSA2026-86), and fixed in Firefox 155. Several of the reported Bugzilla issues showed evidence of memory corruption that Mozilla presumes could have been exploited with sufficient effort to achieve code execution when a user renders malicious web content. There is no public exploit identified at time of analysis and EPSS is low (0.14%), consistent with an internally-found, pre-disclosure fix rather than active abuse.
Memory corruption in the Graphics: ImageLib component of Mozilla Firefox stems from an integer overflow when handling image data, potentially allowing remote attackers to corrupt heap memory and achieve code execution when a victim renders malicious image content. Mozilla fixed the issue in Firefox 155 and Firefox ESR 153.2 (advisories mfsa2026-82/85/86/88). It carries a critical 9.8 CVSS score, but EPSS is only 0.14% (4th percentile), it is not in CISA KEV, and no public exploit was identified at time of analysis.
Cross-origin data exposure in Mozilla Firefox's DOM: Navigation component stems from a site isolation failure that lets malicious web content bypass the same-origin/site boundary Firefox enforces to keep pages from different sites in separate processes. The flaw affects Firefox before version 155 and Firefox ESR before 153.2, and could allow a crafted page to read or influence data belonging to another origin. Reported and fixed by Mozilla (MFSA2026-82/-85/-86/-88); no public exploit identified at time of analysis and EPSS is low (0.14%, 4th percentile).
An improper input validation defect (CWE-20) in Firefox Focus for Android was reported and fixed by Mozilla in Firefox 155 per advisory MFSA2026-82. The public description is a placeholder-grade 'Other issue' with no technical mechanism disclosed, so the concrete impact cannot be verified; there is no public exploit identified at time of analysis and EPSS is low (0.13%, 3rd percentile). Despite a headline CVSS of 9.8, the vendor tag set and thin description leave the real-world severity for this privacy-focused mobile browser unconfirmed.
Information disclosure in Mozilla Firefox's Profile Backup component, remediated in Firefox 155 and Firefox ESR 153.2 (Mozilla advisories MFSA2026-82/85/86/88). Mozilla provides only an 'Other issue' placeholder description, so the precise mechanism is undisclosed, but the CWE-200 classification points to unintended exposure of data handled during profile backup. No public exploit or active exploitation has been identified, and EPSS is very low (0.14%, 4th percentile).
Cross-origin information disclosure in Mozilla Firefox arises from a site-isolation failure in the DOM Push Subscriptions component (CWE-346, origin validation error), allowing content from one origin to be improperly associated with or exposed to another. It affects Firefox before 155 and Firefox ESR before 153.2, and was disclosed and patched by Mozilla; there is no public exploit identified at time of analysis and EPSS is very low (0.14%, 4th percentile). The 'Information Disclosure' tag is consistent with the CWE and the likely cross-origin read impact.
Information disclosure via Firefox's Networking: HTTP component exposes sensitive data to remote unauthenticated attackers in all Firefox versions prior to 155 and all Firefox ESR versions prior to 153.2. The flaw is tracked in Mozilla Bugzilla #2063020 and addressed across four Mozilla security advisories (mfsa2026-82, -85, -86, -88), indicating backport coverage across multiple ESR branches. No public exploit code exists and EPSS probability is very low (0.14%), though the SSVC framework marks the class as automatable.
Information disclosure in Mozilla Firefox's WebGPU graphics component allows remote attackers to read sensitive data - potentially including cross-origin content or GPU memory - by luring a user to a crafted web page. Affected releases are all Firefox versions prior to 155 and Firefox ESR prior to 153.2. Vendor-released patches are available in Firefox 155 and Firefox ESR 153.2; no public exploit code has been identified and the vulnerability is not listed in the CISA KEV catalog.
Cross-origin data exposure in Mozilla Firefox arises from a site-isolation defect in the DOM Navigation component, where origin boundaries are not correctly enforced during navigation, potentially letting a malicious page access data belonging to another origin. It affects Firefox before 155 and Firefox ESR before 153.2, and was fixed by Mozilla in those releases (advisories mfsa2026-82/85/86/88). No public exploit identified at time of analysis; EPSS is low (0.14%, 4th percentile).
Use-after-free in Firefox's WebGPU graphics component allows privilege escalation when a victim visits a specially crafted webpage. Affecting all Firefox versions prior to 155 and ESR prior to 153.2, a remote unauthenticated attacker can trigger memory corruption by delivering malicious WebGPU content, achieving full confidentiality, integrity, and availability impact (CVSS 8.8). No public exploit or active exploitation has been identified at time of analysis; SSVC confirms exploitation status as none and the attack is not automatable due to required user interaction.
Sandbox escape via use-after-free in the Firefox DOM: Security component allows an attacker who lures a victim to a malicious web page to corrupt memory and break out of the browser content sandbox, potentially achieving code execution in a higher-privilege context. All Firefox release and ESR channels prior to the fixed builds are affected. No public exploit identified at time of analysis, and CISA SSVC records exploitation status as none, but the 9.6 CVSS and scope-change sandbox-escape nature make this a high-priority browser update.
Sandbox escape in Mozilla Firefox stems from a use-after-free in the DOM: Navigation component, letting a malicious web page that a user visits corrupt memory and potentially execute code outside the content sandbox. It affects Firefox before 155 and multiple ESR trains (115.x, 140.x, 153.x), carries a critical 9.6 CVSS with a scope change (browser sandbox to host), and requires the victim to load attacker-controlled content (UI:R). No public exploit identified at time of analysis and CISA SSVC lists exploitation as none.
OS command injection in yast2-samba-client through 5.0.4 allows an attacker who controls Active Directory content - via a rogue domain controller or delegated AD object-creation rights - to execute arbitrary commands as root on a SUSE Linux machine during the domain-join process. The attack exploits unsanitized AD directory tree values being passed directly to shell commands running with root privileges inside the YaST2 domain-join workflow. No confirmed KEV status and no public exploit code are available at time of analysis.
OS command injection in SUSE's yast2-auth-client allows an attacker who controls Active Directory configuration values to execute arbitrary commands as root on the target Linux host. The vulnerable code in Auth::AuthConf (src/lib/auth/authconf.rb) constructs Samba net ads join, net ads lookup -S, and net ads testjoin command strings by directly interpolating OU, dnshostname, AD username, and AD domain name values without validation or shell-quoting, then passes the assembled string to Ruby's Open3.popen2 or Open3.capture2, which delegates to /bin/sh. No public exploit has been identified at time of analysis and the vulnerability is not listed in the CISA KEV catalog.
OS command injection in yast2-users (through version 5.0.8) allows root-level arbitrary command execution on SUSE Linux systems when an administrator views a malicious LDAP user's Password Settings tab. The `get_password_term()` function reads `shadowLastChange` and `shadowExpire` LDAP attributes without numeric validation and passes them to `format_days_after_epoch()`, which interpolates the values directly into a shell command executed via Ruby backticks. No public exploit or CISA KEV listing has been confirmed at time of analysis; EPSS data is unavailable.
Remote unauthenticated denial of service in llama.cpp (through commit 97f06e9) allows any network attacker to crash the inference server by submitting a POST request to the /rerank endpoint with a negative top_n value, triggering a std::bad_alloc exception and an HTTP 500 response. The attack surface is exclusively present when the server is started with the non-default --reranking flag. No public exploit has been confirmed at time of analysis, though a public technical writeup exists at ph4nt0m.xyz that details the flaw and may contain proof-of-concept request data.
Privilege escalation in zbus_polkit before 5.1.0 stems from Subject::new_for_owner() encoding the UID as D-Bus type u (unsigned 32-bit) rather than the type i (signed 32-bit) mandated by org.freedesktop.PolicyKit1.Authority, silently nullifying any caller-supplied UID and causing polkit to fall back to a TOCTOU-vulnerable /proc PID lookup. Applications that pass SO_PEERCRED-derived UIDs specifically to defend against PID reuse receive no benefit, as the value is discarded before polkit processes the authorization subject. A local low-privileged attacker who causes an authorized process to exit and wins the PID reassignment race is granted that process's polkit authorization; no public exploit code has been identified at time of analysis.
Out-of-bounds write in Exiv2's RemoteIo::Impl::populateBlocks() affects all versions prior to 0.28.9, exploitable only when Exiv2 is invoked with a remote URL as input rather than a local file path. Memory corruption from the write could theoretically enable code execution in the Exiv2 process context if a user or automated pipeline fetches a specially crafted image from an attacker-controlled server. Fixed in the 0.28.9 release; no public exploit or KEV listing identified at time of analysis.
Authentication denial of service in free5GC AUSF v1.4.4 and current main allows an attacker with access to the AUSF SBI/N12 interface to permanently block a target subscriber from completing 5G authentication by flooding the AUSF with concurrent POST /nausf-auth/v1/ue-authentications requests for the same SUPI. Each concurrent request silently overwrites the active EAP-AKA' session context stored under that SUPI key, so the legitimate UE's EAP response is validated against mismatched cryptographic material (K_aut, XRES) and fails AT_MAC verification. No vendor patch has been released; a working proof-of-concept was reproduced in a controlled lab and is documented in the upstream GHSA advisory, with no CISA KEV listing identified at time of analysis.
Integer overflow in Klever-Go's semi-fungible token (SFT) add-quantity path prior to version 1.7.19 allows a mint-role holder to bypass a finite per-nonce MaxSupply constraint, minting approximately 9.2×10^18 tokens in a single transaction. The SFTAddCirculation function in core/kapp/systemAccount/systemAcount.go increments Circulation before checking the cap, enabling an int64 wraparound that makes the MaxSupply comparison permanently false. A proof-of-concept unit test is included in GHSA-mrpp-v6pg-p54x confirming the bypass; no CISA KEV listing is present at time of analysis.
Token minting without source debit in klever-go's percentage-transfer royalty path (`processPercentageRoyaltiesTransfer`) allows an asset owner who configures a 100% split royalty to cause the blockchain to credit the full royalty amount to an attacker-controlled address on every subsequent transfer by any holder, while the sender debit is silently skipped due to an early-return guard placed before the collection call. The exploit fires automatically on third-party transfers once the asset is configured, enabling unbounded off-books token inflation. A full Go unit test and on-chain transaction trace confirming the mint are publicly available; no CISA KEV listing exists, but the patch's inclusion of a hardcoded freeze list for six specific Klever mainnet addresses strongly implies active exploitation occurred prior to the fix.
Event loop exhaustion in multer (all versions before 2.3.0) allows unauthenticated remote attackers to render a Node.js server completely unresponsive using a single small multipart/form-data request. Two specially crafted field names - a large numeric array index followed by a non-numeric key - cause multer's underlying append-field dependency to synchronously iterate a maximum-length sparse array, permanently blocking the event loop and preventing the process from handling any further requests. No public exploit has been identified at time of analysis, but the attack requires no authentication and a minimal payload, making it trivially automatable against any Node.js application using unpatched multer.
Remote denial-of-service in the Node.js multer middleware (all versions before 2.3.0) allows unauthenticated attackers to crash the entire Node.js process by submitting a small, specially crafted multipart/form-data request. The attack exploits an uncaught RangeError in multer's append-field dependency: a first field with an extremely large numeric index allocates a maximum-length sparse array, and a second field pushes past that limit, throwing an exception that multer does not catch. No public exploit code has been identified at time of analysis, but the zero-authentication, low-complexity nature of the attack makes this a realistic availability threat for any internet-facing Node.js application using multer.
Remote unauthenticated denial-of-service in alos-http, a Linux amd64 Go web framework, allows any network-reachable client to crash the entire server process with a single malformed HTTP request. The flaw exists in the request-line parser's `sanitizeRequestPath` function, which performs an unchecked index into an empty string after stripping a bare query-string path such as `GET ? HTTP/1.1`. Because the panic fires in the connection-worker goroutine before the handler chain, the framework's own `core.Recovery()` middleware cannot intercept it, making the crash total and immediate. A publicly available proof-of-concept exploit exists; the vulnerability is not currently listed in the CISA KEV catalog.
SSRF in the Bifrost AI gateway's multimodal URL-fetch path permits any client that can submit a Bedrock or Vertex provider request to reach internal network services - including cloud instance-metadata endpoints - by supplying IPv6 transition-form addresses (6to4, NAT64) or CGNAT addresses that the `isPublicIP` deny-list in `core/providers/utils/fetch.go` incorrectly classifies as routable public IPs. All releases of the `github.com/maximhq/bifrost/core` Go module prior to v1.5.17 are affected, confirmed on dev HEAD f415c14 (core/version 1.5.15). Publicly available exploit code exists in the GHSA advisory as a runnable Go test; no CISA KEV listing at time of analysis.
NF registration poisoning in free5GC's Network Repository Function (NRF) lets attackers with SBI network access register forged Network Function profiles containing arbitrary, attacker-controlled service endpoint IPs, because the RegisterNFInstance handler performs no field validation against 3GPP TS 29.510. Legitimate NFs (AMF, SMF, AUSF, UDM, PCF, NSSF) then discover the fake profiles via NFDiscover and route control-plane signaling to the attacker, enabling interception, OAuth2 credential harvesting, and denial of service across the entire 5G core service mesh. Publicly available exploit code exists and the vendor has released a patch; the flaw is CWE-20 with a vendor CVSS 4.0 base score of 9.3 (Critical).
Cross-tenant IDOR in Vikunja's kanban task-placement endpoint (POST /api/v1/projects/{project}/views/{view}/buckets/{bucket}/tasks) allows any authenticated user to read the complete contents of any task on the instance and partially mutate its state, defeating Vikunja's project-isolation model. The authorization check in TaskBucket.CanUpdate validates only the URL-scoped project and bucket, never the attacker-controlled task_id supplied in the JSON body; because task IDs are a global sequential integer space, brute-force enumeration of all instance tasks is trivial. This is the fifth documented instance of the same missing-authorization-on-task-child class in Vikunja (siblings: CVE-2026-33676, CVE-2026-33678, CVE-2026-33313, CVE-2026-35598); the vendor-confirmed fix ships in v2.4.0 and no public exploit beyond the detailed advisory proof-of-concept has been identified at time of analysis.
Cross-project Kanban data destruction in Vikunja allows any authenticated user to permanently wipe `task_buckets` and `task_positions` for any project view in the entire instance, regardless of project membership. Affecting versions 0.24.6 through 2.4.0, the `ProjectView.Delete` method performs two unscoped cascading SQL deletes using only the URL-supplied view ID after an authorization check that verifies admin rights on the attacker's own project - never confirming the target view belongs to that project. A working PoC is publicly available via the GHSA advisory; view IDs are auto-increment integers, making full-instance enumeration trivial with no prior reconnaissance.
Unbounded native-token (KLV) minting in the Klever blockchain node (klever-go < 1.7.19) lets any funded account inflate the ledger at will. Split-royalty percentages on a KDA asset are validated by summing per-entry values into a uint32 accumulator with no per-entry cap, so two entries near 0x80000000 wrap the sum below the 10000 (100%) limit and pass validation while each stored percentage stays astronomically large; at payout every split recipient is credited pool × hugePct / 10000 and the negative remainder is silently dropped, minting KLV out of thin air. A full working proof-of-concept is published in the GitHub Security Advisory (GHSA-cgc5-v3f2-8m2v); it is not in CISA KEV and no EPSS score was provided, but the flaw is exploitable on current mainnet and not gated by any fork flag.
Ledger value-creation (KLV minting) in Klever's marketplace settlement affects the klever-go node prior to v1.7.19: because referral and royalty cuts are paid in full while a negative seller remainder is silently dropped, any funded account can settle a self-dealt order whose referral% + royalty% exceeds 100% and mint the surplus into attacker-controlled addresses. Exploitation requires only an ordinary account (PR:L) reachable over the public transaction RPC (CVSS 9.6). Committed regression-test exploit code exists, and the vendor advisory (GHSA-p7gw-2pcp-5pf8) and community monitoring document active mainnet exploitation that minted tens of millions of KLV before an emergency guard was deployed, though this CVE is not listed in CISA KEV.
Unbounded symlink-following in KubeVela's Terraform remote configuration loader allows any principal with `ComponentDefinition` create/update RBAC rights to OOM-kill the cluster-wide vela-core controller and halt all OAM application reconciliation. The root cause (CWE-59) is that `GetTerraformConfigurationFromRemote` in `pkg/controller/utils/capability.go` calls `os.ReadFile` on a symlink target without verifying the target is a regular file or bounding the read size; a repository containing `variables.tf -> /dev/zero` is sufficient to exhaust controller memory before HCL parsing is ever reached. No CISA KEV listing has been identified at time of analysis, but a complete proof-of-concept with exact reproduction commands is publicly disclosed in GHSA-fmgp-q6jx-gg3x, materially lowering the exploitation bar.
Source-address critical option enforcement in golang.org/x/crypto/ssh is incomplete, allowing remote attackers to bypass IP-based access controls on Go-based SSH servers using PasswordCallback, KeyboardInteractiveCallback, NoClientAuthCallback, or GSSAPIWithMICConfig.AllowLogin authentication paths. Versions prior to 0.55.0 silently ignore source-address restrictions returned by these callbacks, defeating an explicit authorization control set by the server application. This is an incomplete fix extending CVE-2026-46595; no public exploit has been identified at time of analysis, and the vulnerability is not listed in CISA KEV.
Denial-of-service in gitoxide's gix-pack crate before 0.69.0 exposes Rust Git clients to remote process crashes during clone or fetch operations via two distinct attack vectors. Unchecked array indexing in the delta application routine causes index-out-of-bounds panics on truncated pack data, while uncapped buffer allocation from attacker-controlled LEB128 size headers allows a 10-byte crafted pack entry to trigger an immediate out-of-memory process kill - both exploitable by any Git server the victim connects to. No active exploitation has been confirmed (not in CISA KEV), but the unauthenticated, network-reachable attack surface with trivial complexity makes this a high-priority patch for any environment running automated clone or fetch workflows against external remotes.
Path traversal and trust inheritance flaws in gitoxide's Rust crates gix (≤ 0.72.0) and gix-validate (≤ 0.10.0) allow an attacker who supplies a malicious repository to read arbitrary git configuration files - including embedded credentials - from a victim system. The attack chains three bugs: a first-occurrence-only `find(b"..")` check in submodule name validation that is bypassed by names like `a..b/../../../.git/`, the fact that this validation function is never invoked in production code, and a trust inheritance flaw in `Submodule::open()` that propagates the parent repository's `Trust::Full` to the traversed path while skipping ownership verification entirely. No public exploit has been identified at time of analysis, though a compiled PoC was referenced (truncated) in the GHSA advisory.
Path traversal in gitoxide before 0.52.1 and gix before 0.83.0 allows an attacker who supplies a malicious git repository to redirect submodule git directory resolution outside .git/modules, exposing arbitrary on-disk repository structure to inspection. The flaw stems from submodule names read from .gitmodules being joined directly as filesystem path components with no normalization or confinement check, so a name such as '../../../escaped-target.git' escapes the expected directory boundary. A proof-of-concept is publicly available via GHSA-fr8x-3vfx-f45h; no confirmed active exploitation at time of analysis.
Index-out-of-bounds panic in gitoxide's gix-packetline library (versions before 0.21.5) allows a malicious Git server to abort the client process during fetch operations by sending a crafted side-band packet line with an empty payload. The TextRef implementation fails to handle zero-length payloads, triggering an unconditional Rust panic that terminates the connecting client. No authentication is required on the attacker's side; the victim need only initiate a fetch or clone against a hostile server. No public exploit code or CISA KEV listing identified at time of analysis.
Credential exfiltration in gitoxide's gix-transport crate allows a server controlling an HTTP redirect response to steal the caller's HTTP Basic Authorization credentials by exploiting a hand-rolled URL parser in gix-url that misidentifies the authority component of crafted redirect URLs. Affected are gix-url versions ≤ 0.32.0 and gix-transport versions ≤ 0.49.0; the redirect identity guard `can_reuse_identity` fails open when the parser does not treat '?' or '#' as authority terminators per RFC 3986, causing credentials to be forwarded to an unintended host. No public exploit has been identified at time of analysis, though the CVSS 4.0 score of 8.7 reflects a full confidentiality impact with no authentication prerequisites.
Deadlock in the Linux kernel's iomap subsystem allows local attackers to cause a denial of service by exhausting the shared bioset used by both iomap_split_ioend and its input bios. The circular dependency in bioset allocation halts I/O completion on iomap-backed filesystems (XFS, ext4 direct I/O) and can hang the affected system. No active exploitation has been confirmed (not in CISA KEV) and the EPSS probability is very low at 0.15% (5th percentile), but the impact on availability is total for the affected I/O path.
Bitmap overflow and incorrect global accounting in the Linux kernel's percpu-km memory allocator (`mm/percpu-km`) allow a local low-privileged attacker on SMP/NUMA systems to corrupt kernel memory, with potential for privilege escalation or kernel crash. Two separate commits introduced the flaws: a63d4ac4ab609 caused `pcpu_create_chunk()` to write beyond the `chunk->populated` bitmap when `nr_units > 1`, and b539b87fed37f introduced the companion `pcpu_nr_empty_pop_pages` accounting error. Fixes have been backported to eight stable kernel branches (5.10.265, 5.15.216, 6.1.183, 6.6.151, 6.12.103, 6.18.44, 7.1.8, 7.2); no public exploit has been identified at time of analysis.
Restriction bypass in the Linux kernel's io_uring subsystem allows a local low-privileged user to shed per-task io_uring security restrictions by executing exec(). When a task that has established io_uring restrictions calls exec(), the kernel's exec cancellation path invokes __io_uring_free(), which incorrectly frees both the task context and the per-task restriction simultaneously. Any io_uring ring created by the post-exec process is then entirely unrestricted, defeating sandbox and policy enforcement intended to constrain io_uring operations. No public exploit has been identified at time of analysis, but the CVSS score of 8.4 with Changed Scope (S:C) reflects that the bypass can expose confidentiality and integrity of resources guarded by the dropped restrictions.
The spi-qpic-snand NAND flash driver in Linux kernel 6.18 and later contains a command-ordering defect that causes every SET_FEATURE write to apply the previous operation's value rather than the intended one, producing an off-by-one effect. On Qualcomm IPQ5018-based hardware (confirmed on TP-Link Archer AX55 v1 with ESMT F50L1G41LB flash), this defect became destructive in v6.18 when SPI-NAND OTP support was introduced: the 'disable OTP mode' call erroneously leaves CFG_OTP_ENABLE set permanently, causing all subsequent flash reads to return OTP area content and all writes to fail with -EIO, rendering the device unbootable. No public exploit identified at time of analysis; EPSS of 0.15% (5th percentile) correctly reflects that this is a driver logic defect rather than a traditionally attacker-controllable vulnerability.
Out-of-bounds memory access in the Linux kernel's ltc4282 hwmon driver exposes systems with this hardware monitor to kernel memory disclosure or destabilization via the VGPIO minimum alarm voltage sysfs read path. A missing return statement in the driver causes the kernel to access memory beyond intended bounds when a local user reads the VGPIO channel's minimum alarm voltage attribute. Patch versions are available across multiple stable branches; no public exploit exists and EPSS sits at 0.17% (6th percentile), indicating very low current exploitation pressure despite the 7.8 CVSS score.
Denial of service in the Linux kernel's MediaTek mtk_eth_soc Ethernet driver: mtk_poll_controller() passed a net_device pointer to mtk_handle_irq_rx(), which expects a struct mtk_eth pointer (the value registered as the request_irq cookie). When CONFIG_NET_POLL_CONTROLLER is enabled and the ndo_poll_controller path is exercised (e.g. via netconsole/netpoll), the resulting bad-pointer dereference crashes the kernel. Only devices using the MediaTek SoC Ethernet driver are affected; there is no public exploit identified at time of analysis and EPSS is low (0.17%, 6th percentile).
Incorrect unit conversion in the RISC-V memory management subsystem causes vmemmap_start_pfn to be computed with a physically misaligned base, violating the mask-alignment requirement for compound_info encoding in the sparse memory model. Linux kernel versions incorporating commit 476849b0fba4 on RISC-V hardware where DRAM base is not aligned to MAX_FOLIO_NR_PAGES × PAGE_SIZE are affected - a condition confirmed on QEMU virt machines and potentially other RISC-V platforms. CVSS 7.8 (AV:L/PR:L/C:H/I:H/A:H) reflects potential local privilege escalation via kernel memory corruption; EPSS of 0.17% (7th percentile) and no CISA KEV listing indicate no observed exploitation activity. No public exploit is identified at time of analysis.
Use-after-free in the Linux kernel's AMD MP2 I2C driver (i2c-amd-mp2) enables local low-privileged users to corrupt kernel memory, potentially achieving privilege escalation or system crash on AMD hardware. The flaw occurs during driver probe: when i2c_add_adapter() fails, devres frees the platform I2C context, but the MP2 PCI driver retains a stale pointer in its IRQ and system-sleep callback table, allowing subsequent dereference of freed memory. No public exploit exists and EPSS is 0.18% (7th percentile), reflecting the hardware-specific and error-path-dependent nature of this flaw; vendor-released patches are available across all major stable kernel branches.
The BPF signed loader in the Linux kernel fails to enforce map exclusivity before performing SHA-based integrity validation of metadata maps, allowing a local attacker with BPF privileges to race a mutation of the shared map's contents after the hash is computed but before validation completes. Systems running Linux kernel between commit fb2b0e290147ba01a53dfd92cf91058c9d2ee254 and the patched stable releases (6.18.40, 7.1.5, 7.2) are affected. Exploitation bypasses the integrity guarantees of the signed BPF loader, enabling the attacker to make the check pass on stale, attacker-controlled data; no public exploit exists and EPSS is 0.17% (6th percentile), indicating low current exploitation probability.
Out-of-bounds kernel memory reads in the Linux kernel's NTFS driver arise because ntfs_read_locked_inode() copies a resident $ATTRIBUTE_LIST into ni->attr_list via a plain memcpy() with no sanity checking, while only the non-resident path was ever validated by load_attribute_list(). A crafted NTFS volume with a malformed resident attribute list is then trusted by every subsequent walk (ntfs_external_attr_find(), ntfs_inode_attach_all_extents(), ntfs_attrlist_need()), which read fixed-header fields past the buffer. The fix factors per-entry validation into ntfs_attr_list_entry_is_valid()/ntfs_attr_list_is_valid() and applies it on the resident path and inside load_attribute_list() itself; no public exploit identified at time of analysis and EPSS probability is very low (0.15%).
Out-of-bounds slab read in the Linux kernel's legacy in-kernel NTFS driver lets a crafted on-disk $ATTRIBUTE_LIST leak or crash adjacent kernel heap memory when a malicious NTFS volume is mounted and read. The flaw is in ntfs_external_attr_find(), where a look-ahead attribute-list entry is dereferenced past the end of the kvmalloc'd buffer. There is no public exploit identified at time of analysis, EPSS risk is low (0.15%, 5th percentile), and it is not listed in CISA KEV.
Out-of-bounds kernel heap read in the Linux kernel's classic in-tree NTFS driver (`fs/ntfs/`) allows a local, low-privileged user to disclose kernel memory - and potentially chain to privilege escalation - by mounting a crafted NTFS image at the filesystem layer. The flaw is a u16 integer truncation in `ntfs_check_restart_area()` that silently defeats a page-size bounds check, causing `ntfs_check_log_client_array()` to dereference up to ~64 KiB beyond an allocated heap buffer using attacker-controlled on-disk values. No public exploit code exists and no active exploitation has been confirmed; EPSS is 0.15% (5th percentile), reflecting negligible observed exploitation pressure.
Out-of-bounds heap read in the Linux kernel's perf userspace tooling (perf tools) lets a crafted perf.data file trigger memory disclosure or a crash when parsed. The flaw sits in machine__resolve(), which trusts an attacker-controlled CPU index (al->cpu) from sample data and indexes env->cpu[] without validating it against env->nr_cpus_avail; a large index reads past the heap allocation, and values like 65536 truncate to int16_t and silently resolve to CPU 0. No public exploit is identified at time of analysis, and EPSS is low (0.18%, 7th percentile).
Availability denial in the Linux kernel's KVM ARM64 nested virtualization stack allows a guest VM to crash the host through improper Synchronous External Abort (SEA) handling when Stage 1 translation resolves a Guest Frame Number outside configured memory slots. Affected systems must run a vulnerable Linux 6.16-era kernel on ARM64 hardware with KVM nested virtualization explicitly enabled; fixed versions are 6.18.40, 7.1.5, and 7.2. No public exploit exists and no active exploitation is confirmed; EPSS stands at 0.18% (7th percentile), reflecting the niche attack surface.
Kernel stack disclosure and potential denial-of-service affect Linux systems with CXL hardware due to an off-by-8 size constant in the CXL RAS capability subsystem introduced in Linux 6.2. A local user who can trigger a CXL AER uncorrectable error and read tracefs can obtain up to 448 bytes of adjacent kernel stack data - potentially including code pointers and sensitive in-flight values - from the tracefs ring buffer. No public exploit identified at time of analysis; EPSS at 0.17% (6th percentile) reflects the niche CXL hardware dependency and local-only attack vector.
Use-after-free in the Linux kernel's UFS (Universal Flash Storage) core tracing subsystem allows a local attacker with tracing access to trigger a kernel crash or potentially achieve privilege escalation. The UFS trace event infrastructure stores raw pointers to the `hba` (Host Bus Adapter) structure in the trace ring buffer, then dereferences those pointers inside `TP_printk()` when `/sys/kernel/tracing/trace` is read - which may occur long after the underlying UFS device has been detached and its memory freed. No public exploit has been identified at time of analysis, and EPSS is 0.17% (6th percentile), indicating low near-term exploitation probability despite the high CVSS score.
Uninitialized-value access in the Linux kernel's HFS+ filesystem driver allows a local attacker with mount privileges to trigger kernel memory corruption or information disclosure by supplying a crafted disk image containing an invalid btree node_size. The flaw is reached during the mount path - specifically in hfsplus_bnode_find() while loading the HFS+ catalog B-tree - when a corrupted node_size value (e.g., 1) causes an excessively large offset to be passed to hfs_bnode_read_u16(), resulting in use of uninitialized stack memory. No public exploit has been identified and EPSS is 0.15% (5th percentile); upstream stable patches are available at git.kernel.org.
Out-of-bounds memory access in the Linux kernel's ARM SCMI firmware subsystem allows a local low-privileged attacker on ARM-based hardware to trigger kernel memory corruption via the scmi_power_name_get() function, which fails to validate the domain number supplied by external callers. Affected kernel versions span from the introduction commit 76a6550990e2 through multiple stable branches, with patches backported to LTS lines 5.15, 6.1, 6.6, 6.12, and 6.18. No public exploit code has been identified at time of analysis, and EPSS probability is very low at 0.17% (7th percentile), indicating no current attacker tooling interest despite the 7.8 CVSS score.
Invalid pointer dereference in the Linux kernel's RapidIO TSI721 driver allows an unauthenticated attacker on an adjacent RapidIO network to crash the kernel or corrupt memory by sending a crafted doorbell message. The root cause is a logic error in tsi721_db_dpc(): the 'found' flag is not reset at the start of each list_for_each() iteration, causing every doorbell after the first match to be treated as found, and causing list-end traversal with an invalid iterator pointer when no match exists. No public exploit exists and EPSS is 0.18% (7th percentile), consistent with the highly constrained physical attack surface; patches are available across multiple stable kernel branches.
Out-of-bounds write in the Linux kernel's OCFS2 cluster filesystem driver corrupts adjacent kernel memory when a low-privileged user unlinks a refcounted file whose refcount tree contains leaf blocks, triggering a fortify panic on hardened kernels. The root cause is an incorrect memset bound in `ocfs2_remove_refcount_extent()` arising from a union aliasing issue between `rf_records.rl_count` and `rf_list.l_tree_depth`. No public exploit or active exploitation has been identified; EPSS is 0.15% (5th percentile) and the vulnerability does not appear in CISA KEV, reflecting low real-world exploitation risk at time of analysis.
Out-of-bounds heap read in the Linux kernel's wcn36xx WiFi driver allows an adjacent-network attacker to corrupt Block Acknowledgment session state by sending crafted 802.11 frames that elicit a short firmware response. Kernels from 4.7 through pre-patch stable branches on devices equipped with Qualcomm WCN3660/WCN3620/WCN3680 WiFi hardware are affected. No public exploit code exists and no CISA KEV listing is present; EPSS of 0.17% (7th percentile) reflects negligible observed exploitation probability consistent with the hardware-specific attack surface.
Missing dma_resv lock acquisition before dma_buf_unpin() in the Linux kernel iommufd subsystem causes a kernel WARN on every IOAS destruction or unmap path that releases the last reference to a DMABUF-backed iopt_pages object. Affected are kernel versions from the commit introducing DMABUF pinning in iommufd (8c5f9645c389) through the fix commits in the 7.1 and 7.2 stable trees, with patches confirmed at Linux 7.1.5 and 7.2. No public exploit or active exploitation has been identified; EPSS is 0.15% (5th percentile), indicating negligible automated exploitation probability at time of analysis.
Use-after-free in the Linux kernel AppArmor subsystem's aa_replace_profiles function exposes kernelspace memory to corruption by a local low-privileged attacker. The defect arises from reading udata->size after aa_put_loaddata(udata) has released the reference - if that release triggers a free, the subsequent read constitutes a UAF that can be leveraged for privilege escalation or arbitrary kernel memory manipulation. EPSS sits at 0.18% (7th percentile) and no CISA KEV listing exists, indicating no confirmed widespread exploitation, though the local-access, low-complexity nature makes this a realistic intrahost threat on AppArmor-enabled systems.
Heap buffer overflow in the Linux kernel's Airoha (airoha_eth) network driver allows the packet-processing engine (PPE) flow-offload logic to write past an undersized allocation, corrupting kernel heap memory and crashing affected systems. The bug affects Linux 6.18.x through 6.18.39 and 6.19/7.x pre-release trees on hardware using the Airoha PPE flow-offload driver, and is triggered when airoha_ppe_foe_verify_entry() processes a flow hash at or above half the entry count. It is not in CISA KEV and has a low EPSS (0.18%), with no public exploit identified at time of analysis; impact is primarily denial of service.
NULL pointer dereference in the Linux kernel's EMAC (Ethernet MAC) network driver during device probe can crash the kernel, resulting in complete system availability loss on affected hardware. The fault lies in `emac_probe()` where `devm_request_irq()` is called before `dev->emacp` is mapped via `devm_platform_ioremap_resource()`, leaving a race window during initialization in which any hardware interrupt invoking `emac_irq()` will dereference a NULL pointer and trigger a kernel panic. No public exploit code exists and the vulnerability is absent from CISA KEV; patches have been released across multiple Linux stable branches.
Metadata corruption in the Linux kernel's lightweight tunnel (LWT) subsystem affects forwarded packets that carry XDP/TC skb metadata when they pass through LWT encapsulation (seg6, rpl, ila, mpls, ioam6, or BPF LWT xmit). Because encapsulation prepends outer headers over the skb headroom where metadata lives, non-BPF encaps silently overwrite it while BPF LWT xmit triggers a skb_data_move() WARNING and clears it; the fix drops metadata at the three LWT dispatch chokepoints before handing the skb to the encap op. There is no public exploit identified at time of analysis, EPSS is low (0.15%), and the nominal CVSS 9.8 appears substantially overstated for what is fundamentally a kernel data-path robustness fix.
Use-after-free race condition in the Linux kernel's amdxdna AMD AI accelerator driver allows a local low-privileged user to trigger kernel memory corruption by racing device removal against GEM object deallocation, potentially achieving full kernel privilege escalation. The flaw is specific to deployments where force_iova mode is enabled in the amdxdna driver, limiting the real-world exposure to systems with AMD XDna-capable hardware. No CISA KEV listing and no public proof-of-concept exist; EPSS of 0.15% (5th percentile) confirms this remains a theoretical priority rather than an active exploitation concern.
Use-after-free in the Linux kernel's batman-adv (B.A.T.M.A.N. advanced) distributed ARP table (DAT) code lets an attacker on the same mesh corrupt kernel memory: batadv_get_vid() calls pskb_may_pull(), which can reallocate the skb buffer, leaving the previously-cached ARP hardware-source pointer dangling and later dereferenced. The flaw affects systems running batman-adv mesh networking across numerous stable kernel branches; a vendor fix reorders the pointer acquisition to occur after the realloc. No public exploit is identified at time of analysis, EPSS is low (0.18%, 7th percentile), and it is not on CISA KEV.
Sandbox escape and out-of-sandbox arbitrary code execution in Google Chrome (desktop) before 152.0.7977.75, rooted in an incorrect authorization flaw in the FileSystem component. A remote attacker who lures a victim into opening a crafted HTML page can break out of the renderer sandbox and run code with the privileges of the browser process. Rated High by Chromium and CVSS 9.6; the vendor has shipped a stable-channel patch, though no public exploit code or active exploitation has been identified at time of analysis.
Sandbox-escaping remote code execution in Google Chrome for Android before 152.0.7977.75 stems from a use-after-free in the Shared Tab Groups feature (CWE-416). A remote attacker who lures a victim into visiting a crafted HTML page can corrupt freed memory to execute arbitrary code outside the renderer sandbox. Chromium rates the severity Critical (CVSS 9.6); the vendor has shipped a fix, but no public exploit has been identified at time of analysis.
Sandbox-escaping remote code execution in Google Chrome for Android before 152.0.7977.75 stems from a use-after-free in the WebGL implementation, letting a remote attacker who lures a victim to a crafted HTML page execute arbitrary code OUTSIDE the renderer sandbox. Rated Critical by Chromium with a CVSS 9.6 (scope-changed) vector; a vendor patch shipped in the September 2026 Stable channel update. No public exploit identified at time of analysis, though the tracker bug (issues.chromium.org/546260492) and Google's own reporting indicate the flaw is well characterized.
Stack-based buffer overflow in the GPU component of Google Chrome on Windows (prior to 152.0.7977.75) enables full sandbox escape and arbitrary code execution on the host operating system. Exploitation is a two-stage chained attack: an attacker must first compromise the renderer process (via a separate vulnerability or exploit), then leverage this GPU flaw to break out of Chrome's sandbox and execute code with elevated host privileges. Google has released a patch in the stable channel update for desktop; no public exploit code or CISA KEV listing has been identified at time of analysis.
Use-after-free in Chrome's TabStrip component enables remote code execution outside the renderer sandbox in Google Chrome versions prior to 152.0.7977.75. An attacker must social-engineer a user into a specific UI interaction to trigger the memory-corruption primitive, after which arbitrary code executes at browser-process privilege - a full sandbox escape. Google has issued a stable channel patch; no public exploit or CISA KEV listing has been identified at time of analysis.
Use-after-free in Google Chrome's Browser process prior to version 152.0.7977.75 enables sandbox escape, allowing an attacker who has already compromised the renderer process to execute arbitrary code outside the Chrome sandbox via a crafted HTML page. The CVSS vector (AV:N/AC:H/S:C/C:H/I:H/A:H) reflects both the network-reachable delivery and the scope change from renderer to host-level execution. No public exploit or CISA KEV listing has been identified at time of analysis, but sandbox-escape primitives of this class are highly valued in exploit chains.
Remote code execution inside Chrome's sandbox is achievable via a use-after-free in WebRTC, triggered when a victim visits a specially crafted HTML page. Affected versions are all Chrome releases prior to 152.0.7977.75 across desktop platforms. No public exploit code or CISA KEV listing has been identified at time of analysis, though the sandboxed execution boundary limits the practical impact compared to the raw CVSS 8.8 score - Google's own Chromium severity rating of 'Medium' reflects this containment.
Sandbox escape in Google Chrome's TabStrip component (versions prior to 152.0.7977.75) allows a remote attacker who has already achieved renderer process compromise to execute arbitrary code outside the Chrome sandbox via incorrect authorization in tab management IPC. The attack chain requires two conditions to be met simultaneously: a prior renderer exploit and social engineering to deliver a crafted HTML page - placing this firmly in the chained-exploit category despite the high CVSS base score. A vendor-released patch is available in Chrome 152.0.7977.75; no public exploit code or active exploitation has been identified at time of analysis.
Sandbox escape in Google Chrome's Chromoting (Chrome Remote Desktop) component on Windows allows a local attacker to execute arbitrary code outside the Chrome sandbox via a crafted local program, affecting all Chrome for Windows versions prior to 152.0.7977.75. The root cause is incorrect authorization (CWE-863) within the Chromoting subsystem, where flawed authorization logic fails to restrict a local program from interacting with Chromoting in a way that crosses the sandbox boundary. Google has released a patched version (152.0.7977.75), and no public exploit has been identified at time of analysis, though the full post-sandbox C:H/I:H/A:H impact warrants prompt remediation.
Remote code execution in Google Chrome for Android before 152.0.7977.75 stems from a use-after-free in Dawn, Chrome's WebGPU/GPU graphics abstraction layer, and - per Google's advisory - allows a crafted HTML page to execute arbitrary code outside the renderer sandbox. Exploitation only requires an unauthenticated victim to visit a malicious page, giving the attacker high-impact code execution on the device. No public exploit has been identified at time of analysis and the issue is not in CISA KEV, though the sandbox-escape framing makes it a high-priority browser patch.
Remote code execution within the browser sandbox is possible in Google Chrome versions prior to 152.0.7977.75 due to a use-of-uninitialized-resource flaw (CWE-908) in the V8 JavaScript engine. An attacker can trigger the vulnerability by luring a user to a crafted HTML page, with no authentication or special privileges required beyond normal web browsing. Google has released the patched build 152.0.7977.75; SSVC rates exploitation status as none and no CISA KEV listing has been identified at time of analysis.
Access-restriction bypass in Google Chrome desktop prior to 152.0.7977.75 lets a remote attacker who first tricks a user via social engineering leverage a co-installed application to escape Chrome's system access boundaries. The flaw is an improper input validation (CWE-20) issue in the browser's DataTransfer component, rated High by Chromium and fixed in the September 2026 Stable channel. EPSS is low (0.16%, 5th percentile), no public exploit or CISA KEV listing exists, so realistic risk is bounded by the required user interaction and the presence of a malicious co-installed app.
Remote code execution in Google Chrome desktop before 152.0.7977.75 stems from a use-after-free in the Proxy component that a remote attacker can trigger with crafted network traffic to run arbitrary code OUTSIDE the browser sandbox. Google rates the Chromium severity High and a patched Stable channel build is available; no public exploit code has been identified at time of analysis. Because the flaw yields a sandbox escape rather than a contained renderer bug, successful exploitation gives attacker-controlled code on the host at browser-process privilege.
Unbounded recursion in Net::DNS before 1.57 for Perl allows a remote unauthenticated attacker to exhaust memory and terminate any DNS forwarder or proxy process by sending a crafted DNS message carrying a TSIG record misplaced in the answer or authority section with an empty MAC field. Because the library's decoder does not drop the malformed packet as RFC 8945 section 5.2 requires, the TSIG survives the re-encoding strip step and drives `sig_data` into infinite recursion; payloads under 100 bytes on the wire are sufficient to crash the process. No public exploit has been identified at time of analysis, and EPSS indicates low current exploitation probability (0.17%), though the trivially small payload and zero-authentication requirement make this an operational priority for any Perl-based DNS forwarder or proxy deployment.
Thunderbird's remote attachment allowlist control (`mail.allowed_attachment_hostnames`) can be bypassed due to insufficient regex escaping of configured hostname values, allowing attacker-controlled servers to serve remote attachments that the filter was intended to block. Affected are all Thunderbird releases prior to 155 and 153.2; because hostname strings containing dots and other regex metacharacters are interpolated directly into a regular expression without sanitization, a crafted attachment hostname can pattern-match an allowlisted domain without being that domain. No public exploit has been identified at time of analysis, and EPSS sits at 0.15% (4th percentile), consistent with low-urgency real-world exploitation risk.
Heap memory disclosure in Mozilla Thunderbird's IMAP client allows a malicious IMAP server to trigger a use-after-free by sending a crafted ID extension response, leaking heap contents that are subsequently persisted to the user's prefs.js file on disk. All Thunderbird releases prior to 155, 140.15 (ESR), and 153.2 across three active release channels are affected. No public exploit or active exploitation has been identified at time of analysis; the EPSS score of 0.15% (4th percentile) reflects low current exploitation probability.
Thunderbird's mail header parser triggers a one-byte buffer over-read (CWE-126) when processing a maliciously crafted message header, potentially exposing a single byte of adjacent heap memory to the sender. All Thunderbird versions across three active release branches are affected until patched - 155, 140.15, and 153.2. No public exploit has been identified and EPSS sits at the 4th percentile, but the network-accessible attack path with no user interaction required keeps this relevant for unpatched deployments.
Use of uninitialized memory in Mozilla Thunderbird's MIME parser allows a remote attacker who sends a specially crafted email to trigger an error condition in certain MIME bodies, causing the client to read uninitialized memory. Depending on what previously occupied that memory, this can leak sensitive process data or crash the application. The flaw was fixed in Thunderbird 155, 140.15 ESR, and 153.2; no public exploit has been identified and EPSS exploitation probability is low (0.15%, 4th percentile).
Arbitrary code execution in Mozilla Thunderbird before 154 (and before ESR 153.2) on Windows allows a crafted calendar (iCalendar) invitation to attach a file:// URI that points at a local or network-hosted executable, bypassing Thunderbird's normal blocking of executable attachments. When the new invitation display is enabled the attachment can also be shown under a misleading, benign-looking filename. No active exploitation is confirmed (not in CISA KEV) and no public exploit code has been identified; EPSS is low at 0.15% (5th percentile).
The BEAM runtime in Erlang/OTP crashes when a remote attacker sends a crafted packet to any exposed TCP port using the inet driver with {packet,4} framing, exploiting a signed integer overflow in packet length calculation inside packet_parser.c and inet_drv.c. Affected deployments span OTP release lines 17 through 29, with vendor-released patches available (27.3.4.17, 28.5.0.6, and 29.0.6); no active exploitation is confirmed in CISA KEV and no public exploit code has been identified at time of analysis. The vendor explicitly characterizes remote code execution as 'extremely unfeasible,' making denial-of-service via VM crash the realistic worst-case impact.
Erlang/OTP's inets HTTP server (httpd) fails to enforce an administrator-configured request body-size limit when processing chunked transfer-encoded requests, enabling unauthenticated remote attackers to exhaust server memory and cause denial of service. Affected OTP branches span 17.x through 27.3.4.16, 28.x through 28.5.0.5, and 29.x through 29.0.5, covering inets versions 5.10 through 9.7.1. No public exploit code has been identified and the CVE is not listed in the CISA KEV catalog, but the zero-authentication, low-complexity network attack path makes this an operationally straightforward DoS risk for any deployment exposing inets httpd to untrusted clients.
Request smuggling in Erlang OTP inets (versions 17.0 through 29.x) arises when the httpd server sits behind a Content-Length-preferring reverse proxy: inets frames the request body by chunked Transfer-Encoding and silently discards a co-present Content-Length header, while the front-end proxies request boundaries by Content-Length, producing a classic CL.TE desync. An unauthenticated network attacker in this topology can inject a crafted prefix into a subsequent victim's HTTP request, potentially enabling session hijacking, credential theft, or cache poisoning against other users of the same back-end. No public exploit has been identified at time of analysis, the vulnerability is not listed in CISA KEV, and vendor patches are available for the OTP 27.x, 28.x, and 29.x release branches.
Remote unauthenticated attackers can exploit Erlang/OTP's built-in inets HTTP server across OTP versions 22.2 through 29.0 to conduct HTTP Request Smuggling by sending headers with whitespace before the colon - a malformed construct the server silently discarded rather than rejecting as mandated by RFC 7230 Section 3.2.4. When inets is deployed behind a front-end proxy or load balancer that interprets such headers differently, the resulting parsing discordance creates a desynchronized request boundary exploitable for session hijacking, authentication bypass, or cache poisoning. No public exploit has been identified at time of analysis; vendor-released patches are available across all three affected OTP release branches.
Memory safety vulnerabilities across multiple internally discovered bugs in Firefox 154 and Firefox ESR 153.1 allow network-based attackers to potentially achieve full browser compromise through memory corruption (CWE-119). Mozilla's own advisory clusters dozens of individual Bugzilla reports - including buffer overflows and related defects - under a single advisory umbrella, noting that sufficiently motivated attackers could likely exploit some of these bugs. Vendor-released patch is available: Firefox 155 and Firefox ESR 153.2. No public exploit identified at time of analysis.
Memory corruption in Mozilla Firefox 154, Firefox ESR 153.1, and Firefox ESR 140.14 stems from a batch of internally discovered memory-safety defects that Mozilla presumes could be exploited to run arbitrary code within the browser process. The flaws were found by Mozilla's own developers and fuzzing efforts (no external report), affect the mainline and both ESR trains, and are resolved in Firefox 155, ESR 140.15, and ESR 153.2. There is no public exploit identified at time of analysis and EPSS exploitation probability is low (0.17%, 6th percentile).
Memory-corruption defects in Mozilla Firefox 154 were discovered internally by Mozilla and bundled under CVE-2026-84142 (advisories MFSA2026-82 and MFSA2026-86), and fixed in Firefox 155. Several of the reported Bugzilla issues showed evidence of memory corruption that Mozilla presumes could have been exploited with sufficient effort to achieve code execution when a user renders malicious web content. There is no public exploit identified at time of analysis and EPSS is low (0.14%), consistent with an internally-found, pre-disclosure fix rather than active abuse.
Memory corruption in the Graphics: ImageLib component of Mozilla Firefox stems from an integer overflow when handling image data, potentially allowing remote attackers to corrupt heap memory and achieve code execution when a victim renders malicious image content. Mozilla fixed the issue in Firefox 155 and Firefox ESR 153.2 (advisories mfsa2026-82/85/86/88). It carries a critical 9.8 CVSS score, but EPSS is only 0.14% (4th percentile), it is not in CISA KEV, and no public exploit was identified at time of analysis.
Cross-origin data exposure in Mozilla Firefox's DOM: Navigation component stems from a site isolation failure that lets malicious web content bypass the same-origin/site boundary Firefox enforces to keep pages from different sites in separate processes. The flaw affects Firefox before version 155 and Firefox ESR before 153.2, and could allow a crafted page to read or influence data belonging to another origin. Reported and fixed by Mozilla (MFSA2026-82/-85/-86/-88); no public exploit identified at time of analysis and EPSS is low (0.14%, 4th percentile).
An improper input validation defect (CWE-20) in Firefox Focus for Android was reported and fixed by Mozilla in Firefox 155 per advisory MFSA2026-82. The public description is a placeholder-grade 'Other issue' with no technical mechanism disclosed, so the concrete impact cannot be verified; there is no public exploit identified at time of analysis and EPSS is low (0.13%, 3rd percentile). Despite a headline CVSS of 9.8, the vendor tag set and thin description leave the real-world severity for this privacy-focused mobile browser unconfirmed.
Information disclosure in Mozilla Firefox's Profile Backup component, remediated in Firefox 155 and Firefox ESR 153.2 (Mozilla advisories MFSA2026-82/85/86/88). Mozilla provides only an 'Other issue' placeholder description, so the precise mechanism is undisclosed, but the CWE-200 classification points to unintended exposure of data handled during profile backup. No public exploit or active exploitation has been identified, and EPSS is very low (0.14%, 4th percentile).
Cross-origin information disclosure in Mozilla Firefox arises from a site-isolation failure in the DOM Push Subscriptions component (CWE-346, origin validation error), allowing content from one origin to be improperly associated with or exposed to another. It affects Firefox before 155 and Firefox ESR before 153.2, and was disclosed and patched by Mozilla; there is no public exploit identified at time of analysis and EPSS is very low (0.14%, 4th percentile). The 'Information Disclosure' tag is consistent with the CWE and the likely cross-origin read impact.
Information disclosure via Firefox's Networking: HTTP component exposes sensitive data to remote unauthenticated attackers in all Firefox versions prior to 155 and all Firefox ESR versions prior to 153.2. The flaw is tracked in Mozilla Bugzilla #2063020 and addressed across four Mozilla security advisories (mfsa2026-82, -85, -86, -88), indicating backport coverage across multiple ESR branches. No public exploit code exists and EPSS probability is very low (0.14%), though the SSVC framework marks the class as automatable.
Information disclosure in Mozilla Firefox's WebGPU graphics component allows remote attackers to read sensitive data - potentially including cross-origin content or GPU memory - by luring a user to a crafted web page. Affected releases are all Firefox versions prior to 155 and Firefox ESR prior to 153.2. Vendor-released patches are available in Firefox 155 and Firefox ESR 153.2; no public exploit code has been identified and the vulnerability is not listed in the CISA KEV catalog.
Cross-origin data exposure in Mozilla Firefox arises from a site-isolation defect in the DOM Navigation component, where origin boundaries are not correctly enforced during navigation, potentially letting a malicious page access data belonging to another origin. It affects Firefox before 155 and Firefox ESR before 153.2, and was fixed by Mozilla in those releases (advisories mfsa2026-82/85/86/88). No public exploit identified at time of analysis; EPSS is low (0.14%, 4th percentile).
Use-after-free in Firefox's WebGPU graphics component allows privilege escalation when a victim visits a specially crafted webpage. Affecting all Firefox versions prior to 155 and ESR prior to 153.2, a remote unauthenticated attacker can trigger memory corruption by delivering malicious WebGPU content, achieving full confidentiality, integrity, and availability impact (CVSS 8.8). No public exploit or active exploitation has been identified at time of analysis; SSVC confirms exploitation status as none and the attack is not automatable due to required user interaction.
Sandbox escape via use-after-free in the Firefox DOM: Security component allows an attacker who lures a victim to a malicious web page to corrupt memory and break out of the browser content sandbox, potentially achieving code execution in a higher-privilege context. All Firefox release and ESR channels prior to the fixed builds are affected. No public exploit identified at time of analysis, and CISA SSVC records exploitation status as none, but the 9.6 CVSS and scope-change sandbox-escape nature make this a high-priority browser update.
Sandbox escape in Mozilla Firefox stems from a use-after-free in the DOM: Navigation component, letting a malicious web page that a user visits corrupt memory and potentially execute code outside the content sandbox. It affects Firefox before 155 and multiple ESR trains (115.x, 140.x, 153.x), carries a critical 9.6 CVSS with a scope change (browser sandbox to host), and requires the victim to load attacker-controlled content (UI:R). No public exploit identified at time of analysis and CISA SSVC lists exploitation as none.
OS command injection in yast2-samba-client through 5.0.4 allows an attacker who controls Active Directory content - via a rogue domain controller or delegated AD object-creation rights - to execute arbitrary commands as root on a SUSE Linux machine during the domain-join process. The attack exploits unsanitized AD directory tree values being passed directly to shell commands running with root privileges inside the YaST2 domain-join workflow. No confirmed KEV status and no public exploit code are available at time of analysis.
OS command injection in SUSE's yast2-auth-client allows an attacker who controls Active Directory configuration values to execute arbitrary commands as root on the target Linux host. The vulnerable code in Auth::AuthConf (src/lib/auth/authconf.rb) constructs Samba net ads join, net ads lookup -S, and net ads testjoin command strings by directly interpolating OU, dnshostname, AD username, and AD domain name values without validation or shell-quoting, then passes the assembled string to Ruby's Open3.popen2 or Open3.capture2, which delegates to /bin/sh. No public exploit has been identified at time of analysis and the vulnerability is not listed in the CISA KEV catalog.
OS command injection in yast2-users (through version 5.0.8) allows root-level arbitrary command execution on SUSE Linux systems when an administrator views a malicious LDAP user's Password Settings tab. The `get_password_term()` function reads `shadowLastChange` and `shadowExpire` LDAP attributes without numeric validation and passes them to `format_days_after_epoch()`, which interpolates the values directly into a shell command executed via Ruby backticks. No public exploit or CISA KEV listing has been confirmed at time of analysis; EPSS data is unavailable.
Remote unauthenticated denial of service in llama.cpp (through commit 97f06e9) allows any network attacker to crash the inference server by submitting a POST request to the /rerank endpoint with a negative top_n value, triggering a std::bad_alloc exception and an HTTP 500 response. The attack surface is exclusively present when the server is started with the non-default --reranking flag. No public exploit has been confirmed at time of analysis, though a public technical writeup exists at ph4nt0m.xyz that details the flaw and may contain proof-of-concept request data.
Privilege escalation in zbus_polkit before 5.1.0 stems from Subject::new_for_owner() encoding the UID as D-Bus type u (unsigned 32-bit) rather than the type i (signed 32-bit) mandated by org.freedesktop.PolicyKit1.Authority, silently nullifying any caller-supplied UID and causing polkit to fall back to a TOCTOU-vulnerable /proc PID lookup. Applications that pass SO_PEERCRED-derived UIDs specifically to defend against PID reuse receive no benefit, as the value is discarded before polkit processes the authorization subject. A local low-privileged attacker who causes an authorized process to exit and wins the PID reassignment race is granted that process's polkit authorization; no public exploit code has been identified at time of analysis.
Out-of-bounds write in Exiv2's RemoteIo::Impl::populateBlocks() affects all versions prior to 0.28.9, exploitable only when Exiv2 is invoked with a remote URL as input rather than a local file path. Memory corruption from the write could theoretically enable code execution in the Exiv2 process context if a user or automated pipeline fetches a specially crafted image from an attacker-controlled server. Fixed in the 0.28.9 release; no public exploit or KEV listing identified at time of analysis.
Authentication denial of service in free5GC AUSF v1.4.4 and current main allows an attacker with access to the AUSF SBI/N12 interface to permanently block a target subscriber from completing 5G authentication by flooding the AUSF with concurrent POST /nausf-auth/v1/ue-authentications requests for the same SUPI. Each concurrent request silently overwrites the active EAP-AKA' session context stored under that SUPI key, so the legitimate UE's EAP response is validated against mismatched cryptographic material (K_aut, XRES) and fails AT_MAC verification. No vendor patch has been released; a working proof-of-concept was reproduced in a controlled lab and is documented in the upstream GHSA advisory, with no CISA KEV listing identified at time of analysis.
Integer overflow in Klever-Go's semi-fungible token (SFT) add-quantity path prior to version 1.7.19 allows a mint-role holder to bypass a finite per-nonce MaxSupply constraint, minting approximately 9.2×10^18 tokens in a single transaction. The SFTAddCirculation function in core/kapp/systemAccount/systemAcount.go increments Circulation before checking the cap, enabling an int64 wraparound that makes the MaxSupply comparison permanently false. A proof-of-concept unit test is included in GHSA-mrpp-v6pg-p54x confirming the bypass; no CISA KEV listing is present at time of analysis.
Token minting without source debit in klever-go's percentage-transfer royalty path (`processPercentageRoyaltiesTransfer`) allows an asset owner who configures a 100% split royalty to cause the blockchain to credit the full royalty amount to an attacker-controlled address on every subsequent transfer by any holder, while the sender debit is silently skipped due to an early-return guard placed before the collection call. The exploit fires automatically on third-party transfers once the asset is configured, enabling unbounded off-books token inflation. A full Go unit test and on-chain transaction trace confirming the mint are publicly available; no CISA KEV listing exists, but the patch's inclusion of a hardcoded freeze list for six specific Klever mainnet addresses strongly implies active exploitation occurred prior to the fix.
Event loop exhaustion in multer (all versions before 2.3.0) allows unauthenticated remote attackers to render a Node.js server completely unresponsive using a single small multipart/form-data request. Two specially crafted field names - a large numeric array index followed by a non-numeric key - cause multer's underlying append-field dependency to synchronously iterate a maximum-length sparse array, permanently blocking the event loop and preventing the process from handling any further requests. No public exploit has been identified at time of analysis, but the attack requires no authentication and a minimal payload, making it trivially automatable against any Node.js application using unpatched multer.
Remote denial-of-service in the Node.js multer middleware (all versions before 2.3.0) allows unauthenticated attackers to crash the entire Node.js process by submitting a small, specially crafted multipart/form-data request. The attack exploits an uncaught RangeError in multer's append-field dependency: a first field with an extremely large numeric index allocates a maximum-length sparse array, and a second field pushes past that limit, throwing an exception that multer does not catch. No public exploit code has been identified at time of analysis, but the zero-authentication, low-complexity nature of the attack makes this a realistic availability threat for any internet-facing Node.js application using multer.
Remote unauthenticated denial-of-service in alos-http, a Linux amd64 Go web framework, allows any network-reachable client to crash the entire server process with a single malformed HTTP request. The flaw exists in the request-line parser's `sanitizeRequestPath` function, which performs an unchecked index into an empty string after stripping a bare query-string path such as `GET ? HTTP/1.1`. Because the panic fires in the connection-worker goroutine before the handler chain, the framework's own `core.Recovery()` middleware cannot intercept it, making the crash total and immediate. A publicly available proof-of-concept exploit exists; the vulnerability is not currently listed in the CISA KEV catalog.
SSRF in the Bifrost AI gateway's multimodal URL-fetch path permits any client that can submit a Bedrock or Vertex provider request to reach internal network services - including cloud instance-metadata endpoints - by supplying IPv6 transition-form addresses (6to4, NAT64) or CGNAT addresses that the `isPublicIP` deny-list in `core/providers/utils/fetch.go` incorrectly classifies as routable public IPs. All releases of the `github.com/maximhq/bifrost/core` Go module prior to v1.5.17 are affected, confirmed on dev HEAD f415c14 (core/version 1.5.15). Publicly available exploit code exists in the GHSA advisory as a runnable Go test; no CISA KEV listing at time of analysis.
NF registration poisoning in free5GC's Network Repository Function (NRF) lets attackers with SBI network access register forged Network Function profiles containing arbitrary, attacker-controlled service endpoint IPs, because the RegisterNFInstance handler performs no field validation against 3GPP TS 29.510. Legitimate NFs (AMF, SMF, AUSF, UDM, PCF, NSSF) then discover the fake profiles via NFDiscover and route control-plane signaling to the attacker, enabling interception, OAuth2 credential harvesting, and denial of service across the entire 5G core service mesh. Publicly available exploit code exists and the vendor has released a patch; the flaw is CWE-20 with a vendor CVSS 4.0 base score of 9.3 (Critical).
Cross-tenant IDOR in Vikunja's kanban task-placement endpoint (POST /api/v1/projects/{project}/views/{view}/buckets/{bucket}/tasks) allows any authenticated user to read the complete contents of any task on the instance and partially mutate its state, defeating Vikunja's project-isolation model. The authorization check in TaskBucket.CanUpdate validates only the URL-scoped project and bucket, never the attacker-controlled task_id supplied in the JSON body; because task IDs are a global sequential integer space, brute-force enumeration of all instance tasks is trivial. This is the fifth documented instance of the same missing-authorization-on-task-child class in Vikunja (siblings: CVE-2026-33676, CVE-2026-33678, CVE-2026-33313, CVE-2026-35598); the vendor-confirmed fix ships in v2.4.0 and no public exploit beyond the detailed advisory proof-of-concept has been identified at time of analysis.
Cross-project Kanban data destruction in Vikunja allows any authenticated user to permanently wipe `task_buckets` and `task_positions` for any project view in the entire instance, regardless of project membership. Affecting versions 0.24.6 through 2.4.0, the `ProjectView.Delete` method performs two unscoped cascading SQL deletes using only the URL-supplied view ID after an authorization check that verifies admin rights on the attacker's own project - never confirming the target view belongs to that project. A working PoC is publicly available via the GHSA advisory; view IDs are auto-increment integers, making full-instance enumeration trivial with no prior reconnaissance.
Unbounded native-token (KLV) minting in the Klever blockchain node (klever-go < 1.7.19) lets any funded account inflate the ledger at will. Split-royalty percentages on a KDA asset are validated by summing per-entry values into a uint32 accumulator with no per-entry cap, so two entries near 0x80000000 wrap the sum below the 10000 (100%) limit and pass validation while each stored percentage stays astronomically large; at payout every split recipient is credited pool × hugePct / 10000 and the negative remainder is silently dropped, minting KLV out of thin air. A full working proof-of-concept is published in the GitHub Security Advisory (GHSA-cgc5-v3f2-8m2v); it is not in CISA KEV and no EPSS score was provided, but the flaw is exploitable on current mainnet and not gated by any fork flag.
Ledger value-creation (KLV minting) in Klever's marketplace settlement affects the klever-go node prior to v1.7.19: because referral and royalty cuts are paid in full while a negative seller remainder is silently dropped, any funded account can settle a self-dealt order whose referral% + royalty% exceeds 100% and mint the surplus into attacker-controlled addresses. Exploitation requires only an ordinary account (PR:L) reachable over the public transaction RPC (CVSS 9.6). Committed regression-test exploit code exists, and the vendor advisory (GHSA-p7gw-2pcp-5pf8) and community monitoring document active mainnet exploitation that minted tens of millions of KLV before an emergency guard was deployed, though this CVE is not listed in CISA KEV.
Unbounded symlink-following in KubeVela's Terraform remote configuration loader allows any principal with `ComponentDefinition` create/update RBAC rights to OOM-kill the cluster-wide vela-core controller and halt all OAM application reconciliation. The root cause (CWE-59) is that `GetTerraformConfigurationFromRemote` in `pkg/controller/utils/capability.go` calls `os.ReadFile` on a symlink target without verifying the target is a regular file or bounding the read size; a repository containing `variables.tf -> /dev/zero` is sufficient to exhaust controller memory before HCL parsing is ever reached. No CISA KEV listing has been identified at time of analysis, but a complete proof-of-concept with exact reproduction commands is publicly disclosed in GHSA-fmgp-q6jx-gg3x, materially lowering the exploitation bar.
Source-address critical option enforcement in golang.org/x/crypto/ssh is incomplete, allowing remote attackers to bypass IP-based access controls on Go-based SSH servers using PasswordCallback, KeyboardInteractiveCallback, NoClientAuthCallback, or GSSAPIWithMICConfig.AllowLogin authentication paths. Versions prior to 0.55.0 silently ignore source-address restrictions returned by these callbacks, defeating an explicit authorization control set by the server application. This is an incomplete fix extending CVE-2026-46595; no public exploit has been identified at time of analysis, and the vulnerability is not listed in CISA KEV.
Denial-of-service in gitoxide's gix-pack crate before 0.69.0 exposes Rust Git clients to remote process crashes during clone or fetch operations via two distinct attack vectors. Unchecked array indexing in the delta application routine causes index-out-of-bounds panics on truncated pack data, while uncapped buffer allocation from attacker-controlled LEB128 size headers allows a 10-byte crafted pack entry to trigger an immediate out-of-memory process kill - both exploitable by any Git server the victim connects to. No active exploitation has been confirmed (not in CISA KEV), but the unauthenticated, network-reachable attack surface with trivial complexity makes this a high-priority patch for any environment running automated clone or fetch workflows against external remotes.
Path traversal and trust inheritance flaws in gitoxide's Rust crates gix (≤ 0.72.0) and gix-validate (≤ 0.10.0) allow an attacker who supplies a malicious repository to read arbitrary git configuration files - including embedded credentials - from a victim system. The attack chains three bugs: a first-occurrence-only `find(b"..")` check in submodule name validation that is bypassed by names like `a..b/../../../.git/`, the fact that this validation function is never invoked in production code, and a trust inheritance flaw in `Submodule::open()` that propagates the parent repository's `Trust::Full` to the traversed path while skipping ownership verification entirely. No public exploit has been identified at time of analysis, though a compiled PoC was referenced (truncated) in the GHSA advisory.
Path traversal in gitoxide before 0.52.1 and gix before 0.83.0 allows an attacker who supplies a malicious git repository to redirect submodule git directory resolution outside .git/modules, exposing arbitrary on-disk repository structure to inspection. The flaw stems from submodule names read from .gitmodules being joined directly as filesystem path components with no normalization or confinement check, so a name such as '../../../escaped-target.git' escapes the expected directory boundary. A proof-of-concept is publicly available via GHSA-fr8x-3vfx-f45h; no confirmed active exploitation at time of analysis.
Index-out-of-bounds panic in gitoxide's gix-packetline library (versions before 0.21.5) allows a malicious Git server to abort the client process during fetch operations by sending a crafted side-band packet line with an empty payload. The TextRef implementation fails to handle zero-length payloads, triggering an unconditional Rust panic that terminates the connecting client. No authentication is required on the attacker's side; the victim need only initiate a fetch or clone against a hostile server. No public exploit code or CISA KEV listing identified at time of analysis.
Credential exfiltration in gitoxide's gix-transport crate allows a server controlling an HTTP redirect response to steal the caller's HTTP Basic Authorization credentials by exploiting a hand-rolled URL parser in gix-url that misidentifies the authority component of crafted redirect URLs. Affected are gix-url versions ≤ 0.32.0 and gix-transport versions ≤ 0.49.0; the redirect identity guard `can_reuse_identity` fails open when the parser does not treat '?' or '#' as authority terminators per RFC 3986, causing credentials to be forwarded to an unintended host. No public exploit has been identified at time of analysis, though the CVSS 4.0 score of 8.7 reflects a full confidentiality impact with no authentication prerequisites.
Deadlock in the Linux kernel's iomap subsystem allows local attackers to cause a denial of service by exhausting the shared bioset used by both iomap_split_ioend and its input bios. The circular dependency in bioset allocation halts I/O completion on iomap-backed filesystems (XFS, ext4 direct I/O) and can hang the affected system. No active exploitation has been confirmed (not in CISA KEV) and the EPSS probability is very low at 0.15% (5th percentile), but the impact on availability is total for the affected I/O path.
Bitmap overflow and incorrect global accounting in the Linux kernel's percpu-km memory allocator (`mm/percpu-km`) allow a local low-privileged attacker on SMP/NUMA systems to corrupt kernel memory, with potential for privilege escalation or kernel crash. Two separate commits introduced the flaws: a63d4ac4ab609 caused `pcpu_create_chunk()` to write beyond the `chunk->populated` bitmap when `nr_units > 1`, and b539b87fed37f introduced the companion `pcpu_nr_empty_pop_pages` accounting error. Fixes have been backported to eight stable kernel branches (5.10.265, 5.15.216, 6.1.183, 6.6.151, 6.12.103, 6.18.44, 7.1.8, 7.2); no public exploit has been identified at time of analysis.
Restriction bypass in the Linux kernel's io_uring subsystem allows a local low-privileged user to shed per-task io_uring security restrictions by executing exec(). When a task that has established io_uring restrictions calls exec(), the kernel's exec cancellation path invokes __io_uring_free(), which incorrectly frees both the task context and the per-task restriction simultaneously. Any io_uring ring created by the post-exec process is then entirely unrestricted, defeating sandbox and policy enforcement intended to constrain io_uring operations. No public exploit has been identified at time of analysis, but the CVSS score of 8.4 with Changed Scope (S:C) reflects that the bypass can expose confidentiality and integrity of resources guarded by the dropped restrictions.
The spi-qpic-snand NAND flash driver in Linux kernel 6.18 and later contains a command-ordering defect that causes every SET_FEATURE write to apply the previous operation's value rather than the intended one, producing an off-by-one effect. On Qualcomm IPQ5018-based hardware (confirmed on TP-Link Archer AX55 v1 with ESMT F50L1G41LB flash), this defect became destructive in v6.18 when SPI-NAND OTP support was introduced: the 'disable OTP mode' call erroneously leaves CFG_OTP_ENABLE set permanently, causing all subsequent flash reads to return OTP area content and all writes to fail with -EIO, rendering the device unbootable. No public exploit identified at time of analysis; EPSS of 0.15% (5th percentile) correctly reflects that this is a driver logic defect rather than a traditionally attacker-controllable vulnerability.
Out-of-bounds memory access in the Linux kernel's ltc4282 hwmon driver exposes systems with this hardware monitor to kernel memory disclosure or destabilization via the VGPIO minimum alarm voltage sysfs read path. A missing return statement in the driver causes the kernel to access memory beyond intended bounds when a local user reads the VGPIO channel's minimum alarm voltage attribute. Patch versions are available across multiple stable branches; no public exploit exists and EPSS sits at 0.17% (6th percentile), indicating very low current exploitation pressure despite the 7.8 CVSS score.
Denial of service in the Linux kernel's MediaTek mtk_eth_soc Ethernet driver: mtk_poll_controller() passed a net_device pointer to mtk_handle_irq_rx(), which expects a struct mtk_eth pointer (the value registered as the request_irq cookie). When CONFIG_NET_POLL_CONTROLLER is enabled and the ndo_poll_controller path is exercised (e.g. via netconsole/netpoll), the resulting bad-pointer dereference crashes the kernel. Only devices using the MediaTek SoC Ethernet driver are affected; there is no public exploit identified at time of analysis and EPSS is low (0.17%, 6th percentile).
Incorrect unit conversion in the RISC-V memory management subsystem causes vmemmap_start_pfn to be computed with a physically misaligned base, violating the mask-alignment requirement for compound_info encoding in the sparse memory model. Linux kernel versions incorporating commit 476849b0fba4 on RISC-V hardware where DRAM base is not aligned to MAX_FOLIO_NR_PAGES × PAGE_SIZE are affected - a condition confirmed on QEMU virt machines and potentially other RISC-V platforms. CVSS 7.8 (AV:L/PR:L/C:H/I:H/A:H) reflects potential local privilege escalation via kernel memory corruption; EPSS of 0.17% (7th percentile) and no CISA KEV listing indicate no observed exploitation activity. No public exploit is identified at time of analysis.
Use-after-free in the Linux kernel's AMD MP2 I2C driver (i2c-amd-mp2) enables local low-privileged users to corrupt kernel memory, potentially achieving privilege escalation or system crash on AMD hardware. The flaw occurs during driver probe: when i2c_add_adapter() fails, devres frees the platform I2C context, but the MP2 PCI driver retains a stale pointer in its IRQ and system-sleep callback table, allowing subsequent dereference of freed memory. No public exploit exists and EPSS is 0.18% (7th percentile), reflecting the hardware-specific and error-path-dependent nature of this flaw; vendor-released patches are available across all major stable kernel branches.
The BPF signed loader in the Linux kernel fails to enforce map exclusivity before performing SHA-based integrity validation of metadata maps, allowing a local attacker with BPF privileges to race a mutation of the shared map's contents after the hash is computed but before validation completes. Systems running Linux kernel between commit fb2b0e290147ba01a53dfd92cf91058c9d2ee254 and the patched stable releases (6.18.40, 7.1.5, 7.2) are affected. Exploitation bypasses the integrity guarantees of the signed BPF loader, enabling the attacker to make the check pass on stale, attacker-controlled data; no public exploit exists and EPSS is 0.17% (6th percentile), indicating low current exploitation probability.
Out-of-bounds kernel memory reads in the Linux kernel's NTFS driver arise because ntfs_read_locked_inode() copies a resident $ATTRIBUTE_LIST into ni->attr_list via a plain memcpy() with no sanity checking, while only the non-resident path was ever validated by load_attribute_list(). A crafted NTFS volume with a malformed resident attribute list is then trusted by every subsequent walk (ntfs_external_attr_find(), ntfs_inode_attach_all_extents(), ntfs_attrlist_need()), which read fixed-header fields past the buffer. The fix factors per-entry validation into ntfs_attr_list_entry_is_valid()/ntfs_attr_list_is_valid() and applies it on the resident path and inside load_attribute_list() itself; no public exploit identified at time of analysis and EPSS probability is very low (0.15%).
Out-of-bounds slab read in the Linux kernel's legacy in-kernel NTFS driver lets a crafted on-disk $ATTRIBUTE_LIST leak or crash adjacent kernel heap memory when a malicious NTFS volume is mounted and read. The flaw is in ntfs_external_attr_find(), where a look-ahead attribute-list entry is dereferenced past the end of the kvmalloc'd buffer. There is no public exploit identified at time of analysis, EPSS risk is low (0.15%, 5th percentile), and it is not listed in CISA KEV.
Out-of-bounds kernel heap read in the Linux kernel's classic in-tree NTFS driver (`fs/ntfs/`) allows a local, low-privileged user to disclose kernel memory - and potentially chain to privilege escalation - by mounting a crafted NTFS image at the filesystem layer. The flaw is a u16 integer truncation in `ntfs_check_restart_area()` that silently defeats a page-size bounds check, causing `ntfs_check_log_client_array()` to dereference up to ~64 KiB beyond an allocated heap buffer using attacker-controlled on-disk values. No public exploit code exists and no active exploitation has been confirmed; EPSS is 0.15% (5th percentile), reflecting negligible observed exploitation pressure.
Out-of-bounds heap read in the Linux kernel's perf userspace tooling (perf tools) lets a crafted perf.data file trigger memory disclosure or a crash when parsed. The flaw sits in machine__resolve(), which trusts an attacker-controlled CPU index (al->cpu) from sample data and indexes env->cpu[] without validating it against env->nr_cpus_avail; a large index reads past the heap allocation, and values like 65536 truncate to int16_t and silently resolve to CPU 0. No public exploit is identified at time of analysis, and EPSS is low (0.18%, 7th percentile).
Availability denial in the Linux kernel's KVM ARM64 nested virtualization stack allows a guest VM to crash the host through improper Synchronous External Abort (SEA) handling when Stage 1 translation resolves a Guest Frame Number outside configured memory slots. Affected systems must run a vulnerable Linux 6.16-era kernel on ARM64 hardware with KVM nested virtualization explicitly enabled; fixed versions are 6.18.40, 7.1.5, and 7.2. No public exploit exists and no active exploitation is confirmed; EPSS stands at 0.18% (7th percentile), reflecting the niche attack surface.
Kernel stack disclosure and potential denial-of-service affect Linux systems with CXL hardware due to an off-by-8 size constant in the CXL RAS capability subsystem introduced in Linux 6.2. A local user who can trigger a CXL AER uncorrectable error and read tracefs can obtain up to 448 bytes of adjacent kernel stack data - potentially including code pointers and sensitive in-flight values - from the tracefs ring buffer. No public exploit identified at time of analysis; EPSS at 0.17% (6th percentile) reflects the niche CXL hardware dependency and local-only attack vector.
Use-after-free in the Linux kernel's UFS (Universal Flash Storage) core tracing subsystem allows a local attacker with tracing access to trigger a kernel crash or potentially achieve privilege escalation. The UFS trace event infrastructure stores raw pointers to the `hba` (Host Bus Adapter) structure in the trace ring buffer, then dereferences those pointers inside `TP_printk()` when `/sys/kernel/tracing/trace` is read - which may occur long after the underlying UFS device has been detached and its memory freed. No public exploit has been identified at time of analysis, and EPSS is 0.17% (6th percentile), indicating low near-term exploitation probability despite the high CVSS score.
Uninitialized-value access in the Linux kernel's HFS+ filesystem driver allows a local attacker with mount privileges to trigger kernel memory corruption or information disclosure by supplying a crafted disk image containing an invalid btree node_size. The flaw is reached during the mount path - specifically in hfsplus_bnode_find() while loading the HFS+ catalog B-tree - when a corrupted node_size value (e.g., 1) causes an excessively large offset to be passed to hfs_bnode_read_u16(), resulting in use of uninitialized stack memory. No public exploit has been identified and EPSS is 0.15% (5th percentile); upstream stable patches are available at git.kernel.org.
Out-of-bounds memory access in the Linux kernel's ARM SCMI firmware subsystem allows a local low-privileged attacker on ARM-based hardware to trigger kernel memory corruption via the scmi_power_name_get() function, which fails to validate the domain number supplied by external callers. Affected kernel versions span from the introduction commit 76a6550990e2 through multiple stable branches, with patches backported to LTS lines 5.15, 6.1, 6.6, 6.12, and 6.18. No public exploit code has been identified at time of analysis, and EPSS probability is very low at 0.17% (7th percentile), indicating no current attacker tooling interest despite the 7.8 CVSS score.
Invalid pointer dereference in the Linux kernel's RapidIO TSI721 driver allows an unauthenticated attacker on an adjacent RapidIO network to crash the kernel or corrupt memory by sending a crafted doorbell message. The root cause is a logic error in tsi721_db_dpc(): the 'found' flag is not reset at the start of each list_for_each() iteration, causing every doorbell after the first match to be treated as found, and causing list-end traversal with an invalid iterator pointer when no match exists. No public exploit exists and EPSS is 0.18% (7th percentile), consistent with the highly constrained physical attack surface; patches are available across multiple stable kernel branches.
Out-of-bounds write in the Linux kernel's OCFS2 cluster filesystem driver corrupts adjacent kernel memory when a low-privileged user unlinks a refcounted file whose refcount tree contains leaf blocks, triggering a fortify panic on hardened kernels. The root cause is an incorrect memset bound in `ocfs2_remove_refcount_extent()` arising from a union aliasing issue between `rf_records.rl_count` and `rf_list.l_tree_depth`. No public exploit or active exploitation has been identified; EPSS is 0.15% (5th percentile) and the vulnerability does not appear in CISA KEV, reflecting low real-world exploitation risk at time of analysis.
Out-of-bounds heap read in the Linux kernel's wcn36xx WiFi driver allows an adjacent-network attacker to corrupt Block Acknowledgment session state by sending crafted 802.11 frames that elicit a short firmware response. Kernels from 4.7 through pre-patch stable branches on devices equipped with Qualcomm WCN3660/WCN3620/WCN3680 WiFi hardware are affected. No public exploit code exists and no CISA KEV listing is present; EPSS of 0.17% (7th percentile) reflects negligible observed exploitation probability consistent with the hardware-specific attack surface.
Missing dma_resv lock acquisition before dma_buf_unpin() in the Linux kernel iommufd subsystem causes a kernel WARN on every IOAS destruction or unmap path that releases the last reference to a DMABUF-backed iopt_pages object. Affected are kernel versions from the commit introducing DMABUF pinning in iommufd (8c5f9645c389) through the fix commits in the 7.1 and 7.2 stable trees, with patches confirmed at Linux 7.1.5 and 7.2. No public exploit or active exploitation has been identified; EPSS is 0.15% (5th percentile), indicating negligible automated exploitation probability at time of analysis.
Use-after-free in the Linux kernel AppArmor subsystem's aa_replace_profiles function exposes kernelspace memory to corruption by a local low-privileged attacker. The defect arises from reading udata->size after aa_put_loaddata(udata) has released the reference - if that release triggers a free, the subsequent read constitutes a UAF that can be leveraged for privilege escalation or arbitrary kernel memory manipulation. EPSS sits at 0.18% (7th percentile) and no CISA KEV listing exists, indicating no confirmed widespread exploitation, though the local-access, low-complexity nature makes this a realistic intrahost threat on AppArmor-enabled systems.
Heap buffer overflow in the Linux kernel's Airoha (airoha_eth) network driver allows the packet-processing engine (PPE) flow-offload logic to write past an undersized allocation, corrupting kernel heap memory and crashing affected systems. The bug affects Linux 6.18.x through 6.18.39 and 6.19/7.x pre-release trees on hardware using the Airoha PPE flow-offload driver, and is triggered when airoha_ppe_foe_verify_entry() processes a flow hash at or above half the entry count. It is not in CISA KEV and has a low EPSS (0.18%), with no public exploit identified at time of analysis; impact is primarily denial of service.
NULL pointer dereference in the Linux kernel's EMAC (Ethernet MAC) network driver during device probe can crash the kernel, resulting in complete system availability loss on affected hardware. The fault lies in `emac_probe()` where `devm_request_irq()` is called before `dev->emacp` is mapped via `devm_platform_ioremap_resource()`, leaving a race window during initialization in which any hardware interrupt invoking `emac_irq()` will dereference a NULL pointer and trigger a kernel panic. No public exploit code exists and the vulnerability is absent from CISA KEV; patches have been released across multiple Linux stable branches.
Metadata corruption in the Linux kernel's lightweight tunnel (LWT) subsystem affects forwarded packets that carry XDP/TC skb metadata when they pass through LWT encapsulation (seg6, rpl, ila, mpls, ioam6, or BPF LWT xmit). Because encapsulation prepends outer headers over the skb headroom where metadata lives, non-BPF encaps silently overwrite it while BPF LWT xmit triggers a skb_data_move() WARNING and clears it; the fix drops metadata at the three LWT dispatch chokepoints before handing the skb to the encap op. There is no public exploit identified at time of analysis, EPSS is low (0.15%), and the nominal CVSS 9.8 appears substantially overstated for what is fundamentally a kernel data-path robustness fix.
Use-after-free race condition in the Linux kernel's amdxdna AMD AI accelerator driver allows a local low-privileged user to trigger kernel memory corruption by racing device removal against GEM object deallocation, potentially achieving full kernel privilege escalation. The flaw is specific to deployments where force_iova mode is enabled in the amdxdna driver, limiting the real-world exposure to systems with AMD XDna-capable hardware. No CISA KEV listing and no public proof-of-concept exist; EPSS of 0.15% (5th percentile) confirms this remains a theoretical priority rather than an active exploitation concern.
Use-after-free in the Linux kernel's batman-adv (B.A.T.M.A.N. advanced) distributed ARP table (DAT) code lets an attacker on the same mesh corrupt kernel memory: batadv_get_vid() calls pskb_may_pull(), which can reallocate the skb buffer, leaving the previously-cached ARP hardware-source pointer dangling and later dereferenced. The flaw affects systems running batman-adv mesh networking across numerous stable kernel branches; a vendor fix reorders the pointer acquisition to occur after the realloc. No public exploit is identified at time of analysis, EPSS is low (0.18%, 7th percentile), and it is not on CISA KEV.