Suse
Monthly
Cache poisoning in BuildKit lets a malicious image advertise DiffIDs that do not match its actual layer contents, so a daemon with a shared or persistent cache can adopt attacker-controlled layers as the base for a victim image and execute attacker code inside the victim build - for example by replacing a commonly executed path such as /bin/sh, reading build secrets mounted into the build, altering output artifacts, or hanging the build. Exploitation is unauthenticated but conditional: the attacker's image must be processed before the victim build on a daemon with a shared or persistent cache (multi-tenant or long-lived CI/build farms), and a victim build must then reference the targeted base image; ephemeral, non-shared caches are unaffected. No public exploit code identified at time of analysis; the vendor patch is BuildKit v0.33.1, and the issue carries a CVSS 7.5 (CVSS 4.0) rating with our independent assessment at CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:L.
Denial of service in Moby BuildKit allows a low-privileged remote user to crash the BuildKit daemon by submitting a build that attempts to use a CDI device when the daemon was started with the --cdi-disabled flag. This triggers a null pointer dereference (CWE-476) and daemon panic. The vulnerability requires a non-default configuration and the ability to submit builds; default deployments are not affected. No public exploit has been identified, and the vendor has released a patch in version 0.33.1.
Remote code execution in LibreOffice Calc allows attackers to execute arbitrary Java code by embedding a crafted external data link that loads a malicious Java database driver from a remote URL when the document is opened. This affects LibreOffice versions prior to the fix that enforces file URLs for Java class-path entries. Exploitation requires user interaction (opening the document) and a local attack vector; no public exploit has been identified at time of analysis, yet the high-severity impact can fully compromise the user's system.
Bouncy Castle for Java before 1.86 fails to tie a Remove proposal in an MLS (RFC 9420) external commit to the joining party, allowing any holder of the group's public GroupInfo to evict an arbitrary member and take over that member's slot in the ratchet tree. Exploitation requires only that an application use the library's MLS module and accept external commits through the public Group.externalJoin / Group.handle API on an affected version; no group membership, credential, or user interaction is needed, and the missing credential check existed only in the gRPC interop harness, protecting none of the other API callers. The vendor rates this 8.7 (CVSS 4.0 AV:N/AC:L/AT:N/PR:N/UI:N), and there is no public exploit identified at time of analysis, though the flaw is trivially reachable by anyone who legitimately receives GroupInfo.
Signature-verification bypass in Bouncy Castle for Java before 1.86 lets a phantom signer be accepted in BLS12-381 aggregate signature verification. The faulty BLS12_381BasicScheme.keyValidate() trusts the public key's own ECCurve object during the prime-order subgroup check, so an attacker-supplied ECPoint built on a foreign curve that merely shares BLS12-381's field characteristic - with its cofactor forged to 1 - passes validation despite not being a G1 point; in the pairing implementation such a point contributes the identity in the target group, so an aggregate signature verifies even though it contains no signature for that key/message pair. The issue is reachable only where an application constructs an ECPoint on an explicit, non-canonical curve and accepts it as an authority-bearing key, since the standard 48-byte compressed-point decoder always supplies the canonical curve; no public exploit has been identified at time of analysis, and the assessed impact is high integrity compromise without confidentiality or availability loss (CVSS:4.0 base 7.1, network vector, no privileges required).
Bouncy Castle for Java's Messaging Layer Security (MLS, RFC 9420) implementation before 1.86 fails to bind an X.509 credential to a LeafNode's signature_key, allowing an unauthenticated remote attacker to present a victim's certificate while signing the LeafNode and KeyPackage with an unrelated key and be accepted under the victim's identity. In an MLS deployment that uses X.509 credentials and admits external commits without an independent credential-admission check, the attacker can be admitted as the victim, evict the victim via resynchronization (which compares whole credentials rather than signing keys), derive the current epoch, decrypt subsequent group messages, and send messages accepted as the victim. The flaw is rated CVSS 9.2 (CVSS:4.0) / 9.2-equivalent high impact with the vendor patch available in 1.86; no public exploit code or confirmed active exploitation was identified at time of analysis, and deployments using only basic credentials are explicitly unaffected. Note the assessed attack complexity is High because the MLS/X.509 path must be in use and the application must lack its own credential-admission validation.
Bouncy Castle for Java 1.81 through 1.85.2 fails to verify that a third-party OpenPGP signature was issued by a component key actually granted certification authority, so the high-level certificate API will attribute an attacker-made certification or trust delegation to the certificate's offline primary key. An attacker must already hold the private key of a restricted subkey (one bound only with SIGN_DATA, or a legacy RSA encryption subkey whose algorithm can still sign) that lacks the RFC 9580 sec. 5.2.3.29 CERTIFY_OTHER flag; they can then issue a positive User ID certification or a full-trust depth-one direct-key delegation that getCertificationBy()/getDelegationBy() report as a valid chain, and any application treating isValid() as an identity or trusted-introducer decision will accept the forged assertion at the primary key's authority. The flaw is a privilege promotion of an already-compromised subkey rather than a key-recovery attack, no public exploit code has been identified at time of analysis, and vendor fixes are available in 1.86.
Signature misattribution in the high-level OpenPGP API of Bouncy Castle for Java before 1.86 lets an attacker who holds a third party's public signing subkey - entirely public material - graft that subkey onto their own primary key with a Subkey Binding signature that omits both the Key Flags subpacket and the embedded Primary Key Binding (cross-certification) signature. Because OpenPGPCertificate.isSigningKey() and verifyEmbeddedPrimaryKeyBinding() resolved the subkey's key flags two different ways, the grafted subkey was treated as signing-capable while being exempt from the cross-certification requirement, so OpenPGPSignature.OpenPGPDocumentSignature.isValid() returned true for a message the subkey genuinely signed and reported the attacker's certificate as its issuer; GnuPG rejects the identical certificate and message. This yields misattribution of an existing genuine signature under an attacker-chosen, self-asserted identity - no private key is recovered and no new signature can be forged - and only affects relying parties that pin trust on the subkey's fingerprint or key ID while taking the signer identity from the enclosing certificate. The vendor rates it 8.2 (CVSS 4.0) with integrity-only impact; an independent assessment scores it CVSS 3.1 8.2-equivalent integrity-only (AC:H, PR:N, UI:N), no public exploit code and no confirmed active exploitation (not in CISA KEV) were identified at time of analysis.
Improper validation of the digestAlgorithm/authAttrs pairing in Bouncy Castle's CMS AuthenticatedData handling lets a man-in-the-middle make the parser return authenticated attributes that the message MAC never covered, in Bouncy Castle for Java before 1.86, Bouncy Castle LTS before 2.73.13, and the BC-FJA/FIPS releases (bcpkix-fips before 1.0.13/2.0.13/2.1.13 and bcutil-fips before 2.0.8/2.1.8). Because the streaming CMSAuthenticatedDataParser picks in its constructor whether the MAC covers the DER encoding of authAttrs or the eContent OCTET STRING based solely on whether digestAlgorithm is present - a field that precedes authAttrs in the SEQUENCE - a message crafted with digestAlgorithm absent but authAttrs present passes the genuine content-MAC check and then exposes attacker-chosen attributes through getAuthAttrs(). Exploitation is unauthenticated at the network layer (CVSS:4.0 PR:N, no keys of either the key-encryption or content-MAC type are needed) but requires an in-transit tampering position and a victim application that makes an authorization, routing, or labelling decision from those attributes; the eContent payload itself remains MAC-bound, no public exploit has been identified at time of analysis, and signals conflict on whether this merits urgent prioritization (vendor CVSS 4.0 8.7 with AC:L versus an independent CVSS 3.1 assessment of AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N).
Certificate-validation bypass in Bouncy Castle for Java lets a PKIXCertPathReviewer accept an end-entity certificate that violates a NameConstraints extension imposed by its own issuing CA, causing isValidCertPath() to return true with an empty error list for a chain the real PKIX validator rejects. Affected are BC-Java before 1.86, BC-LTS-Java before 2.73.13, and BC-FJA (bcpkix-fips) before 1.0.13 / 2.0.13 / 2.1.13; exploitation requires an application that uses org.bouncycastle.pkix.jcajce.PKIXCertPathReviewer (or the legacy org.bouncycastle.x509 copy) to make the trust decision rather than the unaffected CertPathValidator "PKIX"/"BC", and a chain whose leaf actually breaches the CA's permitted or excluded subtrees. No public exploit code has been identified at time of analysis, the vulnerability is unauthenticated (CVSS PR:N) per the vendor vector, and the vendor scores it CVSS 4.0 8.7 (High) for high integrity impact; note that an independent assessment rates attack complexity higher (CVSS 3.1 AV:N/AC:H) because the exposure depends entirely on non-default application architecture rather than on anything the attacker controls.
Truncated OpenPGP messages are silently accepted by Bouncy Castle for Java's OpenPGP decryption streams, letting an attacker who can deliver or truncate a message strip trailing packets and, on the SEIPD version 1 path, suppress the modification detection code check entirely, so recipients are handed unauthenticated CFB-decrypted plaintext. The AEAD route (SEIPD v2 and the version 5 AEAD packet) fails open when a literal data packet ends exactly on an AEAD chunk boundary and the consumer reads in increments smaller than one chunk, while the more severe SEIPDv1 route affects only the high-level org.bouncycastle.openpgp.api present in bc-java, not the LTS or FIPS editions. The vendor rates this CVSS 4.0 8.2 (VI:H, with no confidentiality or availability impact), and the fix is released in bc-java 1.86, bc-lts-java 2.73.13, and bcpg-fips 1.0.14 / 2.0.14.1 / 2.1.14; no public exploit identified at time of analysis.
Workflow-controlled container options in Gitea act_runner let an authenticated user who can trigger a job escape the job container into the runner host, because HostConfig fields such as PidMode=host, IpcMode=host, CapAdd=[ALL] and unconfined seccomp/AppArmor profiles survive the runner's sanitization pass and a job step can then use nsenter to execute commands as root on the host. The flaw specifically defeats the 'runner privileged mode disabled' hardening control, which only forces Privileged=false while sanitizeConfig() filters nothing but Binds and Mounts, so default Docker-backed configurations are affected below v3.0.0 (Go module gitea.com/gitea/runner < 1.0.9-0.20260731160927-34bfa1915022). Publicly available exploit code exists in the form of the advisory's minimal proof-of-concept workflow YAML, but no CISA KEV listing or confirmed active exploitation has been reported; impact scales with tenancy, being critical for shared runners accepting untrusted workflow submissions and lower for single-tenant runners restricted to trusted maintainers.
Uncontrolled resource allocation in Apache Thrift versions before 0.25.0 allows remote unauthenticated attackers to exhaust memory, CPU, or worker/connection capacity in services built on the C++, Java, Go, netstd, Python, and Delphi bindings (CWE-770), disrupting availability. The impact is availability-only - no confidentiality or integrity loss - rated CVSS 8.2 under CVSS 4.0, with the 4.0 AT:P flag and the independent CVSS:3.1 assessment (AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H) both indicating a specific condition must hold for the allocation to trigger, so exploitation is not guaranteed against every message or deployment. No public exploit code and no CISA KEV listing were identified at time of analysis; upgrading to 0.25.0 removes the condition entirely.
Denial of service in the Go language bindings of Apache Thrift affects all versions before 0.25.0, where resources are allocated without limits or throttling, allowing a remote unauthenticated client to exhaust server memory or other resources and take down the service. Per the assessed vector (AV:N/AC:L/PR:N/UI:N, availability-only impact), any Thrift Go server endpoint reachable over the network is exposed, with no confidentiality or integrity consequence; the practical exposure is narrowed by network reachability and by whether the deployment accepts Thrift traffic from untrusted clients. CISA KEV does not list this issue and no public exploit code was identified at time of analysis, so exploitation appears to require only a crafted or excessive-volume Thrift message rather than a published attack tool.
Denial of service in the Java bindings of Apache Thrift (all versions before 0.25.0) allows an accepted protocol peer to exhaust server resources by triggering unbounded allocation while Thrift messages are received and parsed. Per the assessed CVSS vector (PR:L), the attacker must already be an authenticated or otherwise accepted client of the Thrift service rather than an anonymous internet actor, which materially narrows exposure for deployments that only accept connections from trusted peers. The impact ceiling is availability loss only - no data disclosure, integrity impact, or code execution is declared - and no public exploit code or CISA KEV entry is associated with this CVE at time of analysis; the vendor-released fix is version 0.25.0.
Remote, unauthenticated attackers can crash applications built against Apache Thrift's c_glib (C/GLib) language bindings before version 0.25.0 by supplying crafted Thrift protocol input that triggers access of an uninitialized pointer (CWE-824), degrading availability with no confidentiality or integrity impact. The flaw carries a CVSS 4.0 score of 8.7 (assessed as CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), and only deployments that use the c_glib binding and expose a Thrift endpoint to an attacker-reachable network are affected - services using Java, Python, Go or other bindings are not exposed to this particular defect. No public exploit code has been identified at time of analysis and there is no indication of confirmed active exploitation (CISA KEV); a vendor-released patch, version 0.25.0, is available.
Unauthenticated, network-reachable denial of service in Apache Thrift's PHP bindings before 0.25.0 lets attackers crash a Thrift service by sending crafted serialized messages that trigger a stack-based buffer overflow during protocol parsing. The vendor-supplied CVSS 4.0 score of 8.7 reflects high availability impact with no confidentiality or integrity impact (VC:N/VI:N/VA:H) and no privileges or user interaction required (PR:N/UI:N), and the assessed CVSS 3.1 vector agrees (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H). No public exploit code or active exploitation has been identified at time of analysis, and the vendor scope bounds the consequence to service crash/denial of service rather than data disclosure or code execution.
Stack exhaustion in Apache Thrift before 0.25.0 allows remote, unauthenticated attackers to crash processes that deserialize attacker-controlled Thrift messages, because the protocol skip routine in several language bindings fails to apply the binding's recursion limit when skipping unknown fields. The affected bindings are the Python C++ accelerator (the pure-Python protocols are not affected), the PHP library and its thrift_protocol extension, and the Perl, Lua, Smalltalk and OCaml libraries; the CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) confirms the bug is reachable over the network with no privileges or user interaction, but the impact metrics (VC:N/VI:N/VA:H) restrict the consequence to availability loss. There is no code execution or data exposure, no public exploit code and no confirmed active exploitation at time of analysis, and Apache has released version 0.25.0 which restores the recursion limit.
Denial of service in Apache Thrift's c_glib (C/GLib) language bindings before 0.25.0, where a crafted or malformed message reaching the deserialization/parsing path triggers a NULL pointer dereference and uninitialized-variable use that crashes the process. The issue is remotely reachable and unauthenticated (CVSS:4.0 vector AV:N/AC:L/AT:N/PR:N/UI:N with availability-high impact only), so any network-exposed Thrift service built on the c_glib binding is at risk of abrupt termination; confidentiality and integrity are unaffected. Only the c_glib binding is implicated - other Thrift bindings are not affected - and no public exploit code has been identified at time of analysis, with the vendor shipping a fix in 0.25.0.
Heap-based memory corruption in Apache Thrift versions before 0.25.0 lets unauthenticated remote attackers who can send Thrift protocol messages to a parsing service trigger an integer-overflow-driven undersized heap allocation followed by an out-of-bounds write, resulting in a crash (denial of service) or potentially attacker-controlled memory corruption with high confidentiality, integrity, and availability impact. The affected surface is any service that deserializes untrusted Thrift traffic; the CVSS v4.0 score of 9.2 reflects network reachability and no required privileges or user interaction, while the AC:H and AT:P metrics (mirrored by the assessed CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) indicate that a successful exploit depends on crafting malformed messages that reliably hit the overflow condition and on runtime factors such as heap layout, memory limits, and the specific protocol/transport in use. No public exploit code or confirmed active exploitation was identified at time of analysis, but the framework's broad embedding in RPC and serialization pipelines makes prompt upgrade to 0.25.0 the clear priority. Services that never parse Thrift input from untrusted or remote peers are not reachable through this vector.
Denial of service in Apache Thrift's Go bindings (all versions before 0.25.0) allows an unauthenticated remote peer to crash an entire Thrift-serving process by sending a single crafted frame over the TFramedTransport or THeaderTransport. A frame that yields no payload bytes causes the transport to recurse into Read rather than loop, so a peer can drive unbounded recursion with only 4 bytes (declared frame size of zero) or 18 bytes (a header block that fills the frame) until the Go stack limit is hit; the resulting runtime fatal error is not catchable by recover() and kills the process. The impact is availability-only - no confidentiality or integrity effect - and no public exploit code has been identified at time of analysis, though exploitation needs only network reachability to the Thrift listener with no authentication or user interaction (CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/.../VA:H).
Memory exhaustion in Apache Thrift's Node.js and D language WebSocket server transports (all versions before 0.25.0) lets unauthenticated remote attackers commit 513 MiB on a Node.js server, or up to 2 GiB on the D transport, by sending a single ~14-byte frame that merely declares a huge payload length. The transport reads the length out of the WebSocket frame header and allocates that many bytes immediately, before the payload has actually arrived, so an extremely small request causes disproportionate memory growth; in the Node.js case the connection is left open afterwards, allowing the same frame to be resent repeatedly until the service is exhausted or killed. Impact is limited to availability (CVSS 4.0 8.7, CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), no authentication or user interaction is required, and no public exploit code was identified at time of analysis. Affected deployments are those exposing the Thrift WebSocket server transport from the Node.js or D bindings; other Thrift transports and language bindings are out of scope.
Denial of service in Apache Thrift's c_glib (C/GLib) language bindings, affecting all versions before 0.25.0, where a crafted or malformed Thrift message can drive the decoder into an infinite loop with an unreachable exit condition (CWE-835). The issue is remotely reachable and requires no authentication per the published CVSS 4.0 vector (PR:N), though the AT:P attack-requirements flag and our independent CVSS 3.1 assessment (AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H) both indicate a specific input condition must be satisfied rather than arbitrary traffic. Impact is confined to availability - a hung thread, pinned CPU, or resource exhaustion that can stall or crash the service - with no data exposure, modification, or code execution; only applications that compile and use the c_glib bindings are affected, and no public exploit code has been identified at time of analysis. Upgrading to 0.25.0 removes the condition.
Denial of service in the PHP bindings of Apache Thrift before 0.25.0 allows unauthenticated remote attackers to exhaust process stack space and crash the parsing worker by supplying deeply nested or self-referential serialized Thrift messages. The flaw is an uncontrolled recursion (CWE-674) in the deserialization path, rated 8.2 High under CVSS 4.0 (AV:N/AC:L/AT:P/PR:N/UI:N/VA:H, with no confidentiality or integrity impact) and 8.2-equivalent High under the assessed CVSS 3.1 vector (A:H only), confirming that impact is confined to availability. Exploitation is not unconditional: the CVSS 4.0 AT:P attack-requirement flag reflects that the target service must actually accept and deserialize attacker-controllable Thrift payloads through the PHP bindings, so internal services processing only trusted, bounded data are not realistically exposed. There is no public exploit code and no confirmed active exploitation at time of analysis, and a vendor-released fix is available in Apache Thrift 0.25.0.
Denial of service in the Apache Thrift Perl bindings affects all releases before 0.25.0, allowing unauthenticated remote attackers to exhaust CPU or memory resources on services that deserialize attacker-controlled Thrift messages through the Perl language runtime. Only deployments using the Perl bindings are exposed; services built on the Java, Python, C++, or Go bindings are not affected by this specific flaw, and no public exploit code was identified at time of analysis, nor is there any CISA KEV confirmation of active exploitation. Impact is availability-only (no confidentiality or integrity loss), the vendor-released fix is Apache Thrift 0.25.0, and exploitation depends on the malicious input actually reaching the vulnerable parsing routine (the CVSS 4.0 AT:P / assessed AC:H condition).
Services that parse attacker-supplied input through Apache Thrift's Perl bindings before version 0.25.0 can be driven into an uncaught exception, crashing the hosting process or thread and causing a denial of service. The flaw is network-reachable and requires no authentication or user interaction (CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N, score 8.2), but its impact is confined to availability (VA:H) with no confidentiality or integrity effect, and the CVSS 4.0 AT:P metric indicates a specific precondition - the attacker's input must actually reach the vulnerable Perl deserialization/handler path. No public exploit code or confirmed active exploitation was identified at time of analysis, and the issue is resolved by the vendor's 0.25.0 release.
Uncaught exception handling in the Apache Thrift Ruby bindings lets unauthenticated remote attackers crash network-reachable Thrift RPC services running any version before 0.25.0. Per the assessed vector (AV:N/AC:L/PR:N/UI:N), no credentials, user interaction, or special configuration are required: any reachable Thrift Ruby service that parses attacker-supplied protocol messages can be knocked offline, though impact is limited to availability with no confidentiality or integrity loss. The flaw carries a CVSS 4.0 score of 8.7 (High) and an assessed CVSS 3.1 of 7.5, and no public exploit identified at time of analysis; exposure is confined to deployments using the Ruby language bindings rather than Thrift bindings for other languages.
Inefficient algorithmic complexity (CWE-407) in Apache Thrift's Lua bindings prior to version 0.25.0 allows remote, unauthenticated attackers to exhaust CPU and cause denial of service by supplying crafted input that the Lua binding parses. Only deployments that specifically use the Thrift Lua language binding and expose it to attacker-influenced data are affected; applications using other Thrift language bindings (Java, Python, C++, Go, etc.) are not impacted. The impact is limited to availability - no confidentiality or integrity loss is indicated by the assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 8.7), and no public exploit code or confirmed active exploitation was identified at time of analysis.
Denial of service in Apache Thrift's JavaME bindings (versions before 0.25.0) allows unauthenticated remote attackers to exhaust server resources by sending crafted Thrift protocol input, causing service outages. The flaw is CWE-770 (uncontrolled resource allocation) and is limited to availability impact; there is no confidentiality or integrity exposure. No public exploit code or active exploitation has been identified at time of analysis, and upgrading to 0.25.0 resolves the issue.
Unbounded resource allocation in the Ruby bindings of Apache Thrift (versions before 0.25.0) lets unauthenticated remote clients exhaust server memory or CPU by sending Thrift messages whose declared structure or container sizes trigger excessive allocation while the service deserializes them. Only network-reachable services that actually accept and parse untrusted Thrift payloads through the Ruby bindings are exposed, and the impact is confined to availability, with no data disclosure or modification (C:N/I:N/A:H). The Apache Software Foundation has released 0.25.0 as the fix; no public exploit code or confirmed active exploitation was identified at time of analysis, and the vendor rates this 8.2 (High) under CVSS 4.0, while our independent assessment also treats it as High severity but notes a higher attack complexity (AC:H in v3.1 terms) because the attacker must reach a service that parses untrusted Thrift messages.
Denial of service in the Lua language bindings of Apache Thrift before 0.25.0 allows unauthenticated remote attackers to exhaust server resources by sending crafted Thrift messages that trigger uncontrolled allocation or inefficient algorithmic paths. The issue is limited to deployments that actively use the Lua bindings; other language bindings are unaffected. At time of analysis there is no confirmed active exploitation (not in CISA KEV) and no public exploit code identified, and the impact is confined to availability-no data disclosure or code execution.
Denial of service in Apache Thrift Python bindings before 0.25.0 allows unauthenticated remote attackers to hang the service by sending crafted Thrift messages that drive the parser into an infinite loop (CWE-835). Exploitation is network-based but requires a specific condition, such as a particular protocol/transport or malformed message structure, to trigger the loop (AT:P / AC:H). The impact is limited to availability-no data disclosure or code execution-and only services exposing a Thrift endpoint that processes untrusted input using the Python bindings are affected; no public exploit code has been identified at time of analysis.
Denial of service in the Apache Thrift PHP bindings before version 0.25.0 allows unauthenticated remote attackers to exhaust server resources by sending crafted Thrift protocol messages that trigger inefficient algorithmic complexity (CWE-407). The vulnerability affects only applications that use the PHP bindings to deserialize untrusted Thrift input; other language bindings are unaffected. No public exploit code has been identified at the time of analysis, and the CVSS 4.0 AT:P metric indicates a specific attack precondition must be met, so exploitation is not guaranteed against every deployment.
Denial of service in Apache Thrift's Go bindings (versions before 0.25.0) lets unauthenticated remote attackers exhaust memory or CPU by sending highly compressed payloads over a compressed transport, so a tiny request expands into a disproportionately large in-memory buffer (CWE-409 data amplification / decompression bomb). Exploitation is conditional: per the vendor's CVSS 4.0 score the AT:P metric applies, meaning the affected service must actually accept attacker-supplied compressed data (for example a zlib-backed transport carrying untrusted input) - deployments of the Go bindings that do not parse compressed payloads from external sources are not exposed. Impact is availability-only (service crash, hang, or memory exhaustion) with no code execution or data disclosure; no public exploit code and no confirmed active exploitation were identified at time of analysis, and our independent assessment uses a 3.1 vector of AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H reflecting that precondition.
Denial of service in Apache Thrift's Python bindings before 0.25.0 arises from improper handling of highly compressed data (CWE-409), letting a remote, unauthenticated attacker send a small compressed Thrift payload that expands dramatically during parsing and exhausts server memory or CPU. Exploitation requires a service that accepts externally supplied Thrift data and decompresses or size-expands it, and the impact is confined to availability with no data disclosure or code execution. No public exploit code has been identified at time of analysis, and upgrading to 0.25.0 eliminates the vulnerability.
Denial of service in the D-language binding of Apache Thrift (thrift.server.nonblocking.TNonblockingServer) allows unauthenticated remote attackers to crash the server by sending a crafted or malformed message that provokes an uncaught exception and improper resource shutdown. Only deployments built with the D binding at versions before 0.25.0 and specifically using TNonblockingServer are affected, and the impact is limited to availability with no data exposure or modification. No public exploit code has been identified at time of analysis, and the vendor has released version 0.25.0 to fix the issue.
Unauthenticated remote attackers can crash applications that use the Apache Thrift PHP bindings prior to version 0.25.0 by supplying crafted Thrift protocol messages that trigger a NULL pointer dereference (CWE-476). The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) indicates the flaw is remotely reachable with low complexity and requires no authentication or user interaction, but the impact profile is availability-only (VC:N/VI:N/VA:H) - there is no confidentiality or integrity exposure, so the 8.7 score reflects a pure denial-of-service outcome rather than code execution. Exploitation is conditional on the target PHP service actually accepting and deserializing attacker-controlled Thrift input, and no public exploit code has been identified at time of analysis. A vendor patch is available in Apache Thrift 0.25.0, which per the advisory fixes the issue.
Denial of service in Apache Thrift deployments that use the D language bindings before version 0.25.0, where malformed input reaching the service endpoint triggers an uncaught exception, an infinite loop with an unreachable exit condition, and an integer underflow that can crash or hang the service. The assessed impact is availability-only (CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H; vendor CVSS 4.0 base 8.7), meaning unauthenticated remote attackers who can reach a D-bindings Thrift service need no credentials, user interaction, or non-default configuration to cause disruption. Exposure is narrow because only services compiled against the D bindings are affected - Java, Python, C++, Go and other language binding deployments are not - and no public exploit code has been identified at time of analysis.
Denial of service and limited integrity tampering in Apache Thrift before 0.25.0 stem from a combination of an infinite loop (CWE-835) and prototype pollution in the Node.js bindings when the TJSONProtocol deserializer parses crafted JSON. Any application exposing a Thrift service built on the Node.js library with TJSONProtocol enabled on an untrusted, attacker-reachable input path can be driven into an unreachable-exit loop that hangs the process, with secondary risk of object prototype attribute manipulation altering application state; the vulnerability is reachable unauthenticated and without user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N, availability High, integrity Low) and the vendor rates it 8.7. No public exploit code has been identified at time of analysis and the issue is not recorded as actively exploited, though the affected product family and the low attack complexity make it a realistic target for opportunistic scanning. Risk is bounded by deployment: services using TBinaryProtocol, TCompactProtocol or non-Node.js Thrift bindings are not affected by this vector.
Integer underflow in Apache Thrift's C++ THeaderTransport can wrap a length or offset calculation and produce an out-of-bounds write, allowing a network attacker to crash or destabilize services that parse THeader-framed messages. The exposure is narrow: the library must be compiled as a 32-bit binary and must actually use THeaderTransport, while 64-bit builds and services relying on other transports are not affected, so the realistic outcome is denial of service rather than code execution or data disclosure. Affected releases are Apache Thrift before 0.25.0; no public exploit code has been identified at time of analysis, and the vendor's own scoring reflects availability-only impact (VA:H with no confidentiality or integrity effect).
Memory exhaustion in Apache Thrift before 0.25.0 lets unauthenticated remote attackers crash services that deserialize attacker-controlled Thrift messages, and the flaw is present across the Go, netstd, OCaml, Erlang, JavaME, Rust, C++, Java, Kotlin, and D language bindings. The supplied CVSS 4.0 vector (8.7 High) and the independent assessment (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) agree that impact is availability-only: no confidentiality or integrity loss, and no authentication, user interaction, or special configuration is required beyond a reachable endpoint that accepts untrusted Thrift input. No public exploit code was identified at time of analysis and the issue is not confirmed as actively exploited (CISA KEV); the vendor-released fix is version 0.25.0.
Denial of service in Apache Thrift's Erlang bindings affects all releases before 0.25.0, where unauthenticated remote attackers who can reach a Thrift service that parses untrusted serialized input can send deeply nested or otherwise resource-heavy messages that the Erlang deserialization code processes without recursion-depth or allocation limits. The result is uncontrolled recursion and unbounded resource consumption (CWE-674), leading to service crash or hang - availability impact only, with no confidentiality or integrity loss confirmed. Exploitation requires the specific precondition that the target actually parses the attacker-supplied payload (CVSS 4.0 AT:P), and the flaw is confined to the Erlang bindings rather than all Thrift language bindings, so this is a moderate-priority availability issue rather than a top-tier emergency; no public exploit code has been identified at time of analysis, and the vendor-released fix is Apache Thrift 0.25.0.
Denial of service in the Lua language bindings of Apache Thrift allows unauthenticated remote attackers to exhaust CPU resources by supplying pathologically crafted input to a regular-expression or parsing code path in releases before 0.25.0, consistent with CWE-1333 (inefficient regular expression complexity). The CVSS 4.0 vector scores 8.2 with AT:P, indicating that a specific attack prerequisite must be met: the deployment must actually use the Lua bindings and attacker-controlled data must reach the vulnerable parsing path, so exploitation is not fully attacker-controlled. The vendor-released fix is Apache Thrift 0.25.0; no public exploit code was identified at time of analysis and there is no confirmed active exploitation (no CISA KEV listing), with the effective risk concentrated in services that parse untrusted input through the Lua binding.
Denial of service in the Erlang language bindings of Apache Thrift before 0.25.0 allows remote attackers to exhaust server resources through unbounded allocation, degrading or crashing the affected service. The flaw is CWE-770 (Allocation of Resources Without Limits or Throttling) and carries a CVSS v4.0 base score of 8.2; our independent assessment scores it CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H, reflecting a high-availability-only impact that requires a specific crafted message structure (AT:P) rather than arbitrary traffic. Only deployments running a Thrift server compiled with the Erlang bindings and exposed to attacker-reachable network traffic are affected; users of the C++, Java, Python, Go and other bindings are not impacted, and no public exploit code was identified at time of analysis.
An uncaught exception (CWE-248) in Apache Thrift's PHP language bindings before 0.25.0 allows unauthenticated remote attackers to terminate PHP processes that accept arbitrary Thrift protocol input, producing a denial of service with no confidentiality or integrity impact. The assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) means no privileges or user interaction are required against a default deployment that exposes a vulnerable PHP-based Thrift endpoint to untrusted network traffic; the practical prerequisite is that the target actually uses the PHP bindings rather than another language binding. No public exploit code and no confirmed active exploitation were identified at time of analysis, and exploitation potential is bounded to service availability - this is a genuine but limited availability risk rather than a data-breach emergency.
Denial of service in the Apache Thrift PHP bindings before 0.25.0 allows unauthenticated remote attackers who can reach a Thrift service built on those bindings to exhaust server resources via unbounded allocation. The flaw is CWE-770 (allocation of resources without limits or throttling), triggered when the PHP binding processes attacker-controllable message sizes or collections without a cap; impact is limited to availability (VA:H; VC:N/VI:N), meaning no data disclosure or code execution. There is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV), so risk is highest for externally reachable Thrift endpoints that accept untrusted clients. Vendor-released patch: 0.25.0.
Unbounded resource allocation in the Node.js bindings of Apache Thrift (all versions before 0.25.0) allows remote, unauthenticated attackers to exhaust memory and crash an exposed Thrift service by sending a crafted message whose declared quantity/size field is not validated before allocation. Impact is limited to availability: no confidentiality or integrity effect, and no code execution is achievable through this path. Exploitation requires a Node.js binding deployment that actually parses untrusted client input (the assessed AT:P condition), and because only the Node.js bindings below 0.25.0 are affected, deployments using other language bindings or newer versions are not exposed; there is no public exploit code identified at time of analysis and the flaw is not listed as confirmed actively exploited (CISA KEV).
Uncontrolled recursion in Apache Thrift's c_glib (C/GLib) bindings causes stack exhaustion and process crash when a crafted, deeply nested message is deserialized from an untrusted source. Only applications built against the c_glib bindings at versions before 0.25.0 are affected; deployments using the Java, Python, C++ or other language bindings are not impacted by this specific issue. The flaw is availability-only - no confidentiality or integrity loss - and is reachable over the network without authentication (CVSS:4.0 PR:N, AT:P), though exploitation depends on the recursive parsing path being exposed to attacker-controlled input; no public exploit code or confirmed active exploitation was identified at time of analysis.
Repeated, attacker-triggered exceptional conditions in the Apache Thrift Java bindings can leak server-side resources and degrade or exhaust a Thrift RPC service running any version before 0.25.0. The issue is remotely reachable without authentication (CVSS PR:N) and needs no user interaction, but the assessed impact is availability only - there is no confirmed confidentiality or integrity effect, so this is a denial-of-service exposure rather than a data-compromise issue. A CVSS 4.0 attack-requirement flag (AT:P) indicates a specific precondition must be met to drive the vulnerable error path, meaning not every request triggers the leak; the precise condition is not specified in the public advisory text, and no public exploit identified at time of analysis. Deployments not using the Java bindings, or already on 0.25.0 or later, are unaffected.
Uncontrolled recursion in the Dart and Java ME bindings of Apache Thrift before 0.25.0 lets a remote, unauthenticated attacker crash or hang a service by sending a Thrift message containing deeply nested or self-referential structures that exhaust the parser's stack. Impact is availability-only (no confidentiality or integrity effect per the assessed CVSS:3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), and the vulnerable surface is confined to deployments that deserialize untrusted data using the Dart or Java ME bindings, so most Thrift users on Java SE, C++, Python, or Go are not exposed. No public exploit code or confirmed active exploitation was identified at time of analysis; the CVSS 4.0 base score of 8.7 should be read alongside the narrow binding-specific exposure, which makes real-world priority moderate rather than critical.
Denial of service in Apache Thrift before 0.25.0 allows unauthenticated remote attackers to crash or exhaust services running affected language bindings by sending malformed Thrift protocol data. The flaw combines improper length-parameter handling with excessive memory allocation, inefficient algorithmic complexity, uncaught exceptions, and insecure default initialization across the Python, Ruby, Erlang, Lua, Dart, JavaME, Perl, PHP, and D bindings. It is availability-only: no code execution, data disclosure, or data tampering is known from this issue. No public exploit code or confirmed active exploitation was identified at time of analysis; upgrading to 0.25.0 resolves it.
Heap-based buffer overflow in the C++ THeaderTransport of Apache Thrift before 0.25.0 lets a remote, unauthenticated attacker corrupt heap memory when an application enables the non-default ZLIB transform for outgoing frames and poorly compressible, peer-influenced data expands during compression. The copy into the write buffer happens without a bounds check, so oversized input overflows the heap allocation and, for large frames, also reads past the end of the transform buffer; impact scales with frame size and reliable code execution versus a crash depends on heap layout. No public exploit code has been identified at time of analysis, and because exploitation requires the ZLIB write transform precondition (without it the vulnerable copy path is never reached), this is a credible high-priority issue rather than an automatic emergency.
Denial of service in the Apache Thrift PHP bindings before version 0.25.0 lets remote, unauthenticated attackers exhaust CPU and memory on a Thrift-serving PHP application by sending a crafted Thrift message whose declared quantity is never validated. Per the assessed CVSS:3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, vendor CVSS 4.0 base 8.7), the weakness is availability-only: there is no code execution, data exposure, or integrity impact, and only deployments that use the PHP bindings to parse untrusted Thrift input over the network are exposed. No public exploit code or confirmed active exploitation (no CISA KEV listing) was identified at time of analysis, and no EPSS score was supplied; non-PHP Thrift bindings are out of scope for this issue.
Denial of service in Apache Thrift's Python bindings (all versions before 0.25.0) allows remote, unauthenticated clients to force unbounded memory allocation by sending crafted messages that declare oversized containers or strings, crashing or hanging the affected service. The flaw pairs a missing resource limit with an insecure default configuration in which the bindings apply no read or container size cap unless the application explicitly sets one, so any network-reachable Thrift service that accepts untrusted traffic while running on those defaults is exposed. Impact is confined to availability with no confidentiality or integrity effect, and the CVSS 4.0 AT:P component reflects that a specific, not fully attacker-controlled deployment condition must be met; no public exploit code has been identified at time of analysis and the issue is not in CISA KEV.
Remote denial of service against Apache Thrift C++ deployments that use the THeaderProtocol is achievable by sending a crafted frame header to a network-reachable Thrift endpoint, causing a stack-based buffer overflow that crashes the service; the flaw combines CWE-121 with an incorrect bitwise shift of an integer in the same header-parsing code path. Every Apache Thrift release before 0.25.0 ships the vulnerable C++ implementation, although only services that actually use the THeaderProtocol transport are exposed - services built against other Thrift protocols or transports are not affected by this specific code path. The CVSS 4.0 base score is 8.7 on a fully unauthenticated, network-reachable vector with availability-only impact (VC:N/VI:N/VA:H), and no public exploit code or confirmed active exploitation has been identified at time of analysis.
Memory exhaustion in Apache Thrift's THeaderTransport affects all versions before 0.25.0, allowing remote attackers to cause a denial of service. Per the CVSS vector (AV:N/AC:L/PR:N/UI:N), exploitation is unauthenticated and requires no user interaction: an attacker can send crafted messages to a Thrift endpoint that uses THeaderTransport, triggering unreleased memory allocations that accumulate and eventually exhaust server resources. The flaw is rated CVSS 8.7 (4.0) with availability-only impact (VC:N/VI:N/VA:H); no public exploit code has been identified at the time of analysis.
Denial of service in Apache Thrift's Dart bindings (all versions before 0.25.0) lets an unauthenticated remote attacker crash or hang a service by sending a Thrift message whose length or size field declares an excessive allocation. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N, VA:H, score 8.7) confirms the flaw is remotely reachable without authentication or user interaction, but impact is confined to availability - confidentiality and integrity are explicitly rated N, with no data exposure or code execution described in any source. Only deployments that deserialize attacker-supplied Thrift traffic through the Dart bindings are affected, and no public exploit identified at time of analysis.
Denial of service in the Apache Thrift Java bindings before 0.25.0 allows remote, unauthenticated attackers to crash or exhaust resources on a service that deserializes attacker-controlled Thrift messages, because exceptional conditions on the message-handling path are not handled correctly and resource allocation is not bounded or throttled. Only deployments running affected Thrift Java server code on a network-reachable endpoint are at risk; impact is confined to availability (service crash / resource exhaustion) with no loss of confidentiality or integrity, and a specific precondition must hold - the crafted input must reach the vulnerable exception-handling or allocation path rather than any arbitrary request. There is no public exploit identified at time of analysis, and no confirmed active exploitation (CISA KEV); vendor-released patch: 0.25.0.
Denial of service in Apache Thrift's Lua language bindings (all versions before 0.25.0) allows unauthenticated remote attackers to drive unbounded resource allocation by sending protocol messages whose declared length parameter is inconsistent with the actual data, abusing a missing allocation limit (CWE-770). Per the vendor vector (PR:N/UI:N) no credentials or user interaction are required; impact is confined to availability (AV:N/AC:L/PR:N/UI:N with A:H, and no confidentiality or integrity effect), meaning memory or CPU exhaustion and likely process termination rather than data exposure or modification. Only deployments that expose a Thrift service implemented with the Lua bindings are in scope, so services built on Thrift's C++, Java, Python, Go and other bindings are not affected by this specific issue; no public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV, and no EPSS score was supplied for this analysis.
StartTLS handling in 389-ds-base does not discard plaintext bytes buffered before the TLS upgrade, allowing an on-path attacker to inject a crafted LDAP message whose messageID collides with a client's pending bind and causes the client to treat a failed authentication as successful. Red Hat Directory Server 11, 12, and 13 and Red Hat Enterprise Linux 6, 7, 8, 9, and 10 deployments using 389-ds-base with StartTLS are affected. Exploitation requires an on-path network position and timing control during StartTLS negotiation, so the real-world bar is higher than the reported 9.0 base score; no public exploit identified at time of analysis.
Denial of service in 389-ds-base (the LDAP engine shipped with Red Hat Directory Server 11/12/13 and Red Hat Enterprise Linux 6 through 10) lets an unauthenticated remote attacker stall the server's worker-thread pool by sending a complete LDAP operation followed by the opening bytes of an incomplete LDAPMessage on the same connection. The server then hands the connection to a second worker thread before the first worker's result is flushed; the second worker blocks on the connection mutex until nsslapd-ioblocktimeout, so the finished operation's response is never delivered. Repeating this over a handful of connections proportional to the configured worker-thread count exhausts the entire pool under default configuration, denying LDAP service to anonymous and authenticated clients over both plaintext and TLS for as long as the attacker holds the connections; no public exploit code has been identified at time of analysis, and no EPSS or KEV signal accompanies the CVE, though the availability-only impact (CVSS 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) is genuine for any internet- or broad-network-reachable directory server.
Memory-exhaustion denial of service in FasterXML jackson-dataformats-binary affects the Smile binary parser on 2.16.0-and-later releases, where SmileParser buffers an entire JSON object property name in memory through an unconstrained _growArrayTo() call inside _handleLongFieldName() and never calls StreamReadConstraints.validateNameLength(), so the configured maxNameLength is silently ignored for this format. Any remote, unauthenticated attacker whose bytes reach SmileFactory parsing - directly or through an ObjectMapper configured with the Smile module - can embed a single unbounded property name and force heap exhaustion, because maxDocumentLength is also disabled by default (CVSS 3.1: 7.5, AV:N/AC:L/PR:N/UI:N, availability-only impact), leaving upload capacity and available heap as the only practical limits. No public exploit identified at time of analysis, and applications that parse only standard JSON are unaffected since jackson-core's JSON parsers enforce maxNameLength incrementally during name decoding.
Memory-exhaustion denial of service in the FasterXML jackson-dataformats-binary CBOR parser allows an unauthenticated remote attacker to force unbounded heap allocation by submitting a CBOR document containing a single property name of arbitrary length; the parser buffers the entire name in memory before returning it because maxNameLength is never validated for this binary format. The defect affects jackson-dataformats-binary running against jackson-core 2.16.0 or later (releases before 2.16.0 never contained the constraint that is left unenforced), and is reachable under default configuration because StreamReadConstraints.maxDocumentLength is disabled by default, leaving no built-in bound on the name. Per the assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5) there is no confidentiality or integrity impact, and the practical damage ceiling is set by the attacker's upload capacity versus the victim's available heap; no public exploit code was identified at time of analysis, and exploitation requires only that attacker-controlled bytes actually reach CBORFactory or an ObjectMapper configured with the CBOR module.
Denial of service in Apache HTTP Server releases before 2.4.69, where the mod_xml2enc filter dereferences a NULL pointer when a proxied response declares a charset whose conversion partially succeeds and then fails, crashing the handling child process. Per the assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L), the crash is reachable without credentials over the network, but exploitation is gated by a trust boundary: the request path must run proxied backend responses through mod_xml2enc (in practice mod_proxy_html content rewriting), and the attacker must control or have compromised that upstream backend server - ordinary external clients cannot directly trigger it. Impact is limited to availability (worker/child process termination with no confidentiality or integrity effect), and no public exploit code, KEV listing, or EPSS score was provided at time of analysis, so this is best treated as a low-to-moderate priority hardening item for reverse-proxy deployments that transform untrusted upstream content.
An integer overflow in the mod_dav_fs module of Apache HTTP Server through 2.4.68 allows an authenticated WebDAV client with write access to crash worker processes and persistently corrupt a directory's property database by sending PROPPATCH requests that declare a large number of XML namespaces. The flaw is a CWE-190 integer overflow; the assessed vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H) confirms the attacker must be authenticated with write permissions, and impact is limited to denial of service and property database integrity, with no code execution, privilege escalation, or data disclosure. No CVSS score, EPSS probability, KEV listing, or public exploit code is present in the provided data, so there is no confirmed active exploitation and no public exploit identified at time of analysis.
Concurrent Digest authentication requests against Apache HTTP Server before 2.4.69 can corrupt authentication state via a use-after-free in the mod_auth_digest module, yielding low integrity and availability impact with no confidentiality impact (per the assessed vector AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L). Unauthenticated remote clients can reach the flaw, but exploitation is gated by two non-default preconditions: AuthDigestNcCheck must be enabled or AuthDigestNonceLifetime set to 0, and the attacker must win a timing-dependent race by sending concurrent Digest requests - serial requests will not reliably trigger it. There is no public exploit identified at time of analysis, no EPSS score, no CISA KEV entry, and no vendor-supplied CVSS, so the sole source is the Apache advisory; the fix is version 2.4.69.
Authentication bypass in the mod_auth_digest module of Apache HTTP Server 2.4.x allows a man-in-the-middle attacker to capture a victim's HTTP Digest authentication credentials and replay them to impersonate that user against the server. Exploitation is conditional: the server must have mod_auth_digest enabled and the non-default directive AuthDigestNonceLifetime must be explicitly set to 0, and the attacker must additionally occupy a network interception position to capture the digest exchange and send crafted requests that force garbage collection of the client's shared-memory nonce entry. The assessed vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N) reflects high confidentiality impact but a high attack-complexity and MITM prerequisite; no public exploit code and no confirmed active exploitation were identified at time of analysis, and the source supplied no CVSS score or EPSS estimate.
Apache HTTP Server 2.4.0 through 2.4.68 can leak a client's session cookie to an upstream backend server through the mod_session_cookie module when the effective value of the SessionCookieRemove directive changes as a request passes through an internal redirect (for example via mod_rewrite or mod_proxy rewrites). The exposure is unauthenticated from the network perspective (PR:N in both the NVD vector and our independent vector), but it is strictly conditional: it requires httpd to be deployed as a proxy/front end in front of a backend, mod_session_cookie to be loaded, SessionCookieRemove to be configured, and that configuration to differ between the pre- and post-redirect contexts - our assessment therefore rates it AC:H with C:L rather than the NVD's AC:L/C:H, since the consequence is a trust-boundary leak of the cookie to the backend rather than direct confidentiality loss to an external attacker. CISA SSVC records Exploitation: none, and no public exploit code has been identified at time of analysis, so this is a genuine-but-conditional hardening issue rather than an urgent, actively exploited priority.
Inconsistent interpretation of HTTP responses in Apache HTTP Server's mod_proxy_uwsgi module lets a crafted backend uwsgi response that carries a Transfer-Encoding header be parsed differently by Apache than by the backend, enabling HTTP response smuggling and desynchronization between the proxy and downstream clients. Affected deployments are Apache HTTP Server 2.4.30 through 2.4.68 configured as a reverse proxy to a uwsgi backend via mod_proxy_uwsgi; installations that do not load or use mod_proxy_uwsgi are not affected. The assessed vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N) is network-reachable by unauthenticated remote attackers, but exploitation is gated by high complexity because the attacker must control or influence the backend uwsgi response - typically through a malicious or compromised backend application, or a response-header-injection flaw in it - so this is not reachable against a default Apache install. No public exploit code has been identified and there is no indication of confirmed active exploitation (no CISA KEV listing); impact is limited to low confidentiality and low integrity with a scope change, not full remote code execution or denial of service.
Stack-based buffer overflow in the mod_vhost_alias module of Apache HTTP Server through 2.4.68 allows a remote, unauthenticated client to crash the server or potentially execute arbitrary code by sending an HTTP request whose Host header exceeds 8192 bytes. The flaw is not reachable in default deployments: the operator must have configured VirtualDocumentRoot (or VirtualScriptAlias) with a hostname format specifier such as %0 or %1 and must have raised LimitRequestFieldSize above its 8192-byte default, a non-default and uncommon combination that is reflected in the assessed vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. No KEV listing, EPSS score, or public exploit code was available at time of analysis, so there is no public exploit identified at time of analysis; the dominant uncertainty is the absence of any quantitative exploitation signal, while the real-world exploitability is sharply constrained by the required operator-set configuration. Users are advised to upgrade to 2.4.69, which fixes the issue.
Forward proxy deployments of Apache HTTP Server through 2.4.68 that relay FTP traffic can be manipulated by an untrusted FTP server into opening a data connection to an arbitrary third-party host, because mod_proxy_ftp fails to validate the address returned in an FTP PASV reply. Only non-default configurations with forward proxying enabled (ProxyRequests On) and mod_proxy_ftp loaded are affected, and the primary impact is a misdirected outbound data connection rather than compromise of the proxy host itself. No KEV entry, EPSS score, or POC was supplied and no public exploit has been identified at time of analysis, so prioritization signals are limited and authentication requirements are not confirmed from the supplied data.
Improper privilege management in Apache HTTP Server's mod_ssl (versions 2.4.0 through 2.4.68) causes SSLRequire access-control directives that use file-related expressions to be evaluated in a way that can grant or deny access contrary to the server operator's intent, giving a remote attacker a possible means to reach content that the SSLRequire check was meant to protect or, conversely, to disrupt intended authorization. The flaw is not reachable in a default configuration: exploitation requires mod_ssl to be loaded and the operator to have configured access control specifically through the SSLRequire directive using file-related expressions, a non-default, operator-chosen configuration, which is reflected in the assessed vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N (high attack complexity, low confidentiality and integrity impact, no availability impact); authentication requirements for the attacker are not confirmed from available data. There is no CISA KEV listing and no public exploit code identified at time of analysis, and no EPSS score was provided.
An out-of-bounds write in Apache HTTP Server 2.4.0 through 2.4.68 on Windows can corrupt memory when the server processes request paths containing MS-DOS 8.3 short filenames that expand to longer names, giving a remote attacker a route to service disruption (assessed availability impact High) with limited confidentiality and integrity impact. Exploitation is Windows-only and conditional: 8.3 short-name generation must be enabled on the underlying NTFS volume (the historical default unless NtfsDisable8dot3NameCreation has been set) and the crafted path must actually reach the expanding-path code path, which is reflected in the assessed vector's AC:H. Apache published no CVSS score, and the supplied intelligence contains no CISA KEV listing, no public exploit code, and no EPSS probability, so there is no public exploit identified at time of analysis.
Use-after-free in Apache HTTP Server's mod_http2 module (versions 2.4.0 through 2.4.68) allows unauthenticated remote attackers to corrupt memory and crash server worker processes by driving re-entrant access to a shared per-session buffer. The flaw only manifests when mod_http2 is loaded and HTTP/2 is actually enabled (h2 and/or h2c in the Protocols directive), and the trigger requires specific concurrent/streamed HTTP/2 request patterns, so the assessed vector is network-reachable but high complexity (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H) with impact limited to availability. No public exploit code or active exploitation has been identified at time of analysis, and no EPSS score was supplied.
Denial of service in Apache HTTP Server 2.4.0 through 2.4.68 arises from a use-after-free in the mod_rewrite module that is reachable only when a RewriteRule or RewriteCond uses the lookahead variables %{LA-U:...} or %{LA-F:...}, which exercise an internal subrequest code path. An unauthenticated remote attacker who can reach a server configured that way can trigger the memory error and crash request-handling processes, degrading or halting service; the independent assessment rates this CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H, so impact is confined to availability and the high attack complexity combined with the non-default configuration prerequisite substantially limits real-world exploitability. No CVSS score or vector has been published by NVD or the vendor, there is no EPSS probability and no CISA KEV listing, and no public exploit code has been identified at time of analysis.
An out-of-bounds write in Apache HTTP Server's optional mod_charset_lite module (affecting versions 2.4.0 through 2.4.68) can corrupt process memory when character-set translation is configured, potentially crashing the server or enabling limited data disclosure or modification. Exposure is narrow: mod_charset_lite is not loaded in default installations and must be explicitly enabled and bound to a content path via directives such as CharsetSourceEnc, CharsetDefault, or an associated input/output filter, which is why the assessed vector rates attack complexity as high (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L). Independent signals are otherwise sparse - no public exploit code, no CISA KEV listing, and no EPSS score were available - so no public exploit identified at time of analysis, and the practical severity hinges on whether the module is deployed.
Out-of-bounds write in the NVIDIA Virtual GPU Manager (vGPU plugin) lets an unprivileged user inside an assigned guest VM corrupt host-side memory by sending a specially crafted RPC call across the virtualization channel, resulting in privilege escalation, data tampering, and denial of service on the host. Rated CVSS 7.3 (AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H), the bug is only reachable in vGPU/VDI/cloud-GPU deployments where the host runs the vGPU plugin and has at least one guest assigned; it is not a network-facing flaw and does not affect standard bare-metal Linux GPU driver installs, and no public exploit code has been identified at time of analysis. Real-world risk is therefore defined by the attack surface rather than by mass exploitability, since a successful attack requires an attacker to already hold an unprivileged local account inside a hosted guest VM.
Incorrect resource transfer between spheres in the NVIDIA vGPU Virtual GPU Manager for Linux allows a locally positioned, low-privileged attacker to break an internal resource-handling boundary and gain high-integrity impact - code execution, privilege escalation, data tampering, information disclosure, or denial of service on the host running the vGPU Manager. This affects virtualization/vGPU deployments on Linux (the manager component on the hypervisor host), not standard desktop GPU drivers, and the CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.8) confirms the attacker must already hold local low-privileged access to a context served by that manager, such as a guest VM or a local account on the host; there is no network or unauthenticated path. It is a genuine local privilege-escalation class issue rather than a remotely triggerable one, and no public exploit was identified at time of analysis.
An out-of-bounds read in the kernel-mode layer of the NVIDIA vGPU Virtual GPU Manager for Linux lets a local attacker who can already reach the vGPU kernel interface trigger memory reads past the bounds of an allocated buffer, potentially yielding information disclosure, data tampering, privilege escalation, denial of service, or kernel code execution. The flaw is rated CVSS 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning it is only reachable by an authenticated local principal - a low-privileged user or a guest context on the hypervisor - and not by an unauthenticated remote network attacker. Exposure is limited to hosts that actually deploy NVIDIA vGPU on Linux (VDI and cloud-GPU virtualization platforms), where the highest-impact scenario is a multi-tenant deployment in which the over-read crosses tenant isolation boundaries; no public exploit code or CISA KEV entry was identified at time of analysis, so this is a genuine but not emergency-grade issue warranting scheduled patching.
Local privilege escalation, code execution, denial of service, information disclosure, and data tampering are possible in NVIDIA GPU Display Driver for Linux due to a use-after-free in the open-source kernel module's event-delivery path. An authenticated local user with access to NVIDIA GPU device nodes can race asynchronous event delivery against file close (CVSS 7.0, AV:L/AC:H/PR:L/UI:N), though the high attack complexity makes success non-deterministic and typically requires repeated attempts; no public exploit has been identified at time of analysis. Risk is concentrated on Linux hosts using the affected open-source kernel module, particularly multi-tenant vGPU, VDI, and cloud GPU deployments.
Local privilege escalation in the NVIDIA GPU Display Driver for Linux kernel-mode layer allows an already-present local user or code-execution foothold (PR:L) to write to memory that should be read-only because memory permissions are not preserved, potentially achieving code execution and elevated privileges on affected GeForce, RTX/Quadro/NVS, and Tesla systems, including vGPU Guest Driver deployments. Exploitation requires local access and high attack complexity, with no remote or unauthenticated network path; no public exploit was identified at time of analysis and the CVE is not listed in CISA KEV. The vendor-supplied CVSS vector uses AV:P while our independent assessment uses AV:L, so the physical-access requirement should be confirmed against NVIDIA bulletin 5861.
Denial of service and kernel memory disclosure in the NVIDIA GPU Display Driver for Windows and Linux let a local, low-privileged user who already holds an interactive session on the host force the kernel-mode component to dereference an untrusted pointer, crashing the driver or leaking kernel memory. The flaw is scored CVSS 3.1 7.1 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H) - a local-only, low-complexity attack requiring low-privilege authenticated access with no user interaction, delivering high confidentiality and availability impact but no integrity or write primitive, so it cannot by itself be chained into privilege escalation or code execution. No public exploit code has been identified and there is no confirmed active exploitation (no CISA KEV listing); the most exposed deployments are multi-user, VDI, and cloud-GPU hosts where untrusted users share a GPU, since the attacker must first obtain code execution or an interactive session on the GPU host.
Authenticated low-privileged local users can bypass cryptographic signature verification in the kernel-mode layer of the NVIDIA GPU Display Driver for Linux when the system is under memory pressure, leading to data tampering and denial of service. The flaw affects GeForce, RTX/Quadro/NVS, and Tesla driver branches on Linux; no public exploit code has been identified at time of analysis. Our assessment rates this as a genuine but bounded-priority local issue because the attacker must reliably induce a low-memory kernel state at the moment of verification, making exploitation opportunistic rather than dependable.
Local privilege escalation in NVIDIA GPU Display Driver for Windows and Linux can be achieved by an unprivileged local user through the open-source kernel module's DMA-BUF import path, where importing a read-only buffer from another device's DMA-BUF exporter improperly preserves memory access permissions. Successful exploitation can result in code execution, privilege escalation, denial of service, information disclosure, and data tampering, with CVSS 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). No public exploit identified at time of analysis, and no CISA KEV entry is present in the provided data.
Local privilege escalation and kernel-level code execution in the NVIDIA GPU Display Driver for Windows and Linux, where the kernel-mode layer follows an error-handling path that operates on an improperly initialized resource (CWE-908). The flaw is reachable by an authenticated, low-privileged local user (CVSS 3.1: AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.8 HIGH) on any host where the affected driver is installed and loaded, granting full confidentiality, integrity, and availability impact within the kernel-mode driver's scope. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (not in CISA KEV); risk is concentrated on shared multi-tenant GPU hosts such as VDI, cloud GPU instances, and vGPU guests where untrusted local users coexist with the driver, and success may be probabilistic because the attacker must reliably trigger the failing error path.
Local privilege escalation in the NVIDIA GPU Display Driver for Linux (open-source kernel module variant) allows any unprivileged local user with an account on the host to abuse a DMA mapping code path where memory access permissions are not properly preserved, potentially yielding code execution, privilege escalation, denial of service, information disclosure, or data tampering. The vulnerability is rated CVSS 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning exploitation requires only local access, no user interaction, and no elevated privileges to trigger, but it is confined to systems running the open-source kernel module - the proprietary module is not affected. There is no public exploit identified at time of analysis and no CISA KEV listing; risk is concentrated in multi-user, VDI, cloud-GPU, and HPC hosts where untrusted local users share GPU-equipped machines.
Local privilege escalation in the NVIDIA GPU Display Driver's open-source kernel module lets an unprivileged local user trigger a use-after-free in the Resource Server map cleanup path via a missing self-reference guard, yielding code execution, privilege escalation, denial of service, information disclosure and data tampering (CVSS 3.1 7.8, AV:L/AC:L/PR:L/UI:N, CWE-416). Affected are Windows and Linux hosts running the open-source kernel module variant of the driver, spanning GeForce, RTX/Quadro/NVS and Tesla product lines per the published CPEs; exploitation requires only a normal local account and no user interaction, but is strictly local with no network vector. No public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis, and the practical risk is highest in shared or multi-tenant GPU environments (vGPU, VDI, cloud GPU) where gaining kernel-level control of the GPU driver crosses a meaningful tenant boundary.
Local privilege escalation in NVIDIA GPU Display Driver for Linux allows an authenticated local unprivileged user to write to memory that the kernel-mode display driver should keep read-only because permissions are not preserved (CWE-281), potentially causing code execution, privilege escalation, denial of service, information disclosure, or data tampering. The affected CPE branches are GeForce, RTX/Quadro/NVS, Tesla, and Guest Driver on Linux, with CVSS 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) indicating high impact after local access. No public exploit identified at time of analysis, and the practical risk is a genuine but not emergency-grade local privilege-escalation issue, most meaningful in shared or multi-tenant GPU environments.
Local privilege escalation and potential code execution in NVIDIA GPU Display Driver for Windows and Linux arise from a use-after-free (CWE-416) reachable by a low-privileged local user who can issue a crafted sequence of driver commands. The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) rates confidentiality, integrity, and availability impact as high, with the greatest risk in shared or virtualized GPU deployments where guest-driver or virtual GPU manager isolation may be broken. No public exploit code or confirmed active exploitation is identified in the available data, and EPSS is not provided; exploitation requires local access and construction of the specific command sequence.
An out-of-bounds read in the kernel-mode layer of NVIDIA GPU Display Driver on Windows and Linux allows a local, authenticated unprivileged user to potentially achieve code execution, privilege escalation, denial of service, information disclosure, or data tampering. Affected products include GeForce, RTX/Quadro/NVS, and Tesla GPUs, as well as Guest Driver and vGPU Manager deployments. With a CVSS score of 7.8, the vulnerability requires local access and low privileges (CVSS vector AV:L/AC:L/PR:L/UI:N), making it primarily a risk in multi-user or shared-GPU environments; no public exploit has been identified at time of analysis, and patched driver branches are available in NVIDIA security bulletin 5861.
Cache poisoning in BuildKit lets a malicious image advertise DiffIDs that do not match its actual layer contents, so a daemon with a shared or persistent cache can adopt attacker-controlled layers as the base for a victim image and execute attacker code inside the victim build - for example by replacing a commonly executed path such as /bin/sh, reading build secrets mounted into the build, altering output artifacts, or hanging the build. Exploitation is unauthenticated but conditional: the attacker's image must be processed before the victim build on a daemon with a shared or persistent cache (multi-tenant or long-lived CI/build farms), and a victim build must then reference the targeted base image; ephemeral, non-shared caches are unaffected. No public exploit code identified at time of analysis; the vendor patch is BuildKit v0.33.1, and the issue carries a CVSS 7.5 (CVSS 4.0) rating with our independent assessment at CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:L.
Denial of service in Moby BuildKit allows a low-privileged remote user to crash the BuildKit daemon by submitting a build that attempts to use a CDI device when the daemon was started with the --cdi-disabled flag. This triggers a null pointer dereference (CWE-476) and daemon panic. The vulnerability requires a non-default configuration and the ability to submit builds; default deployments are not affected. No public exploit has been identified, and the vendor has released a patch in version 0.33.1.
Remote code execution in LibreOffice Calc allows attackers to execute arbitrary Java code by embedding a crafted external data link that loads a malicious Java database driver from a remote URL when the document is opened. This affects LibreOffice versions prior to the fix that enforces file URLs for Java class-path entries. Exploitation requires user interaction (opening the document) and a local attack vector; no public exploit has been identified at time of analysis, yet the high-severity impact can fully compromise the user's system.
Bouncy Castle for Java before 1.86 fails to tie a Remove proposal in an MLS (RFC 9420) external commit to the joining party, allowing any holder of the group's public GroupInfo to evict an arbitrary member and take over that member's slot in the ratchet tree. Exploitation requires only that an application use the library's MLS module and accept external commits through the public Group.externalJoin / Group.handle API on an affected version; no group membership, credential, or user interaction is needed, and the missing credential check existed only in the gRPC interop harness, protecting none of the other API callers. The vendor rates this 8.7 (CVSS 4.0 AV:N/AC:L/AT:N/PR:N/UI:N), and there is no public exploit identified at time of analysis, though the flaw is trivially reachable by anyone who legitimately receives GroupInfo.
Signature-verification bypass in Bouncy Castle for Java before 1.86 lets a phantom signer be accepted in BLS12-381 aggregate signature verification. The faulty BLS12_381BasicScheme.keyValidate() trusts the public key's own ECCurve object during the prime-order subgroup check, so an attacker-supplied ECPoint built on a foreign curve that merely shares BLS12-381's field characteristic - with its cofactor forged to 1 - passes validation despite not being a G1 point; in the pairing implementation such a point contributes the identity in the target group, so an aggregate signature verifies even though it contains no signature for that key/message pair. The issue is reachable only where an application constructs an ECPoint on an explicit, non-canonical curve and accepts it as an authority-bearing key, since the standard 48-byte compressed-point decoder always supplies the canonical curve; no public exploit has been identified at time of analysis, and the assessed impact is high integrity compromise without confidentiality or availability loss (CVSS:4.0 base 7.1, network vector, no privileges required).
Bouncy Castle for Java's Messaging Layer Security (MLS, RFC 9420) implementation before 1.86 fails to bind an X.509 credential to a LeafNode's signature_key, allowing an unauthenticated remote attacker to present a victim's certificate while signing the LeafNode and KeyPackage with an unrelated key and be accepted under the victim's identity. In an MLS deployment that uses X.509 credentials and admits external commits without an independent credential-admission check, the attacker can be admitted as the victim, evict the victim via resynchronization (which compares whole credentials rather than signing keys), derive the current epoch, decrypt subsequent group messages, and send messages accepted as the victim. The flaw is rated CVSS 9.2 (CVSS:4.0) / 9.2-equivalent high impact with the vendor patch available in 1.86; no public exploit code or confirmed active exploitation was identified at time of analysis, and deployments using only basic credentials are explicitly unaffected. Note the assessed attack complexity is High because the MLS/X.509 path must be in use and the application must lack its own credential-admission validation.
Bouncy Castle for Java 1.81 through 1.85.2 fails to verify that a third-party OpenPGP signature was issued by a component key actually granted certification authority, so the high-level certificate API will attribute an attacker-made certification or trust delegation to the certificate's offline primary key. An attacker must already hold the private key of a restricted subkey (one bound only with SIGN_DATA, or a legacy RSA encryption subkey whose algorithm can still sign) that lacks the RFC 9580 sec. 5.2.3.29 CERTIFY_OTHER flag; they can then issue a positive User ID certification or a full-trust depth-one direct-key delegation that getCertificationBy()/getDelegationBy() report as a valid chain, and any application treating isValid() as an identity or trusted-introducer decision will accept the forged assertion at the primary key's authority. The flaw is a privilege promotion of an already-compromised subkey rather than a key-recovery attack, no public exploit code has been identified at time of analysis, and vendor fixes are available in 1.86.
Signature misattribution in the high-level OpenPGP API of Bouncy Castle for Java before 1.86 lets an attacker who holds a third party's public signing subkey - entirely public material - graft that subkey onto their own primary key with a Subkey Binding signature that omits both the Key Flags subpacket and the embedded Primary Key Binding (cross-certification) signature. Because OpenPGPCertificate.isSigningKey() and verifyEmbeddedPrimaryKeyBinding() resolved the subkey's key flags two different ways, the grafted subkey was treated as signing-capable while being exempt from the cross-certification requirement, so OpenPGPSignature.OpenPGPDocumentSignature.isValid() returned true for a message the subkey genuinely signed and reported the attacker's certificate as its issuer; GnuPG rejects the identical certificate and message. This yields misattribution of an existing genuine signature under an attacker-chosen, self-asserted identity - no private key is recovered and no new signature can be forged - and only affects relying parties that pin trust on the subkey's fingerprint or key ID while taking the signer identity from the enclosing certificate. The vendor rates it 8.2 (CVSS 4.0) with integrity-only impact; an independent assessment scores it CVSS 3.1 8.2-equivalent integrity-only (AC:H, PR:N, UI:N), no public exploit code and no confirmed active exploitation (not in CISA KEV) were identified at time of analysis.
Improper validation of the digestAlgorithm/authAttrs pairing in Bouncy Castle's CMS AuthenticatedData handling lets a man-in-the-middle make the parser return authenticated attributes that the message MAC never covered, in Bouncy Castle for Java before 1.86, Bouncy Castle LTS before 2.73.13, and the BC-FJA/FIPS releases (bcpkix-fips before 1.0.13/2.0.13/2.1.13 and bcutil-fips before 2.0.8/2.1.8). Because the streaming CMSAuthenticatedDataParser picks in its constructor whether the MAC covers the DER encoding of authAttrs or the eContent OCTET STRING based solely on whether digestAlgorithm is present - a field that precedes authAttrs in the SEQUENCE - a message crafted with digestAlgorithm absent but authAttrs present passes the genuine content-MAC check and then exposes attacker-chosen attributes through getAuthAttrs(). Exploitation is unauthenticated at the network layer (CVSS:4.0 PR:N, no keys of either the key-encryption or content-MAC type are needed) but requires an in-transit tampering position and a victim application that makes an authorization, routing, or labelling decision from those attributes; the eContent payload itself remains MAC-bound, no public exploit has been identified at time of analysis, and signals conflict on whether this merits urgent prioritization (vendor CVSS 4.0 8.7 with AC:L versus an independent CVSS 3.1 assessment of AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N).
Certificate-validation bypass in Bouncy Castle for Java lets a PKIXCertPathReviewer accept an end-entity certificate that violates a NameConstraints extension imposed by its own issuing CA, causing isValidCertPath() to return true with an empty error list for a chain the real PKIX validator rejects. Affected are BC-Java before 1.86, BC-LTS-Java before 2.73.13, and BC-FJA (bcpkix-fips) before 1.0.13 / 2.0.13 / 2.1.13; exploitation requires an application that uses org.bouncycastle.pkix.jcajce.PKIXCertPathReviewer (or the legacy org.bouncycastle.x509 copy) to make the trust decision rather than the unaffected CertPathValidator "PKIX"/"BC", and a chain whose leaf actually breaches the CA's permitted or excluded subtrees. No public exploit code has been identified at time of analysis, the vulnerability is unauthenticated (CVSS PR:N) per the vendor vector, and the vendor scores it CVSS 4.0 8.7 (High) for high integrity impact; note that an independent assessment rates attack complexity higher (CVSS 3.1 AV:N/AC:H) because the exposure depends entirely on non-default application architecture rather than on anything the attacker controls.
Truncated OpenPGP messages are silently accepted by Bouncy Castle for Java's OpenPGP decryption streams, letting an attacker who can deliver or truncate a message strip trailing packets and, on the SEIPD version 1 path, suppress the modification detection code check entirely, so recipients are handed unauthenticated CFB-decrypted plaintext. The AEAD route (SEIPD v2 and the version 5 AEAD packet) fails open when a literal data packet ends exactly on an AEAD chunk boundary and the consumer reads in increments smaller than one chunk, while the more severe SEIPDv1 route affects only the high-level org.bouncycastle.openpgp.api present in bc-java, not the LTS or FIPS editions. The vendor rates this CVSS 4.0 8.2 (VI:H, with no confidentiality or availability impact), and the fix is released in bc-java 1.86, bc-lts-java 2.73.13, and bcpg-fips 1.0.14 / 2.0.14.1 / 2.1.14; no public exploit identified at time of analysis.
Workflow-controlled container options in Gitea act_runner let an authenticated user who can trigger a job escape the job container into the runner host, because HostConfig fields such as PidMode=host, IpcMode=host, CapAdd=[ALL] and unconfined seccomp/AppArmor profiles survive the runner's sanitization pass and a job step can then use nsenter to execute commands as root on the host. The flaw specifically defeats the 'runner privileged mode disabled' hardening control, which only forces Privileged=false while sanitizeConfig() filters nothing but Binds and Mounts, so default Docker-backed configurations are affected below v3.0.0 (Go module gitea.com/gitea/runner < 1.0.9-0.20260731160927-34bfa1915022). Publicly available exploit code exists in the form of the advisory's minimal proof-of-concept workflow YAML, but no CISA KEV listing or confirmed active exploitation has been reported; impact scales with tenancy, being critical for shared runners accepting untrusted workflow submissions and lower for single-tenant runners restricted to trusted maintainers.
Uncontrolled resource allocation in Apache Thrift versions before 0.25.0 allows remote unauthenticated attackers to exhaust memory, CPU, or worker/connection capacity in services built on the C++, Java, Go, netstd, Python, and Delphi bindings (CWE-770), disrupting availability. The impact is availability-only - no confidentiality or integrity loss - rated CVSS 8.2 under CVSS 4.0, with the 4.0 AT:P flag and the independent CVSS:3.1 assessment (AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H) both indicating a specific condition must hold for the allocation to trigger, so exploitation is not guaranteed against every message or deployment. No public exploit code and no CISA KEV listing were identified at time of analysis; upgrading to 0.25.0 removes the condition entirely.
Denial of service in the Go language bindings of Apache Thrift affects all versions before 0.25.0, where resources are allocated without limits or throttling, allowing a remote unauthenticated client to exhaust server memory or other resources and take down the service. Per the assessed vector (AV:N/AC:L/PR:N/UI:N, availability-only impact), any Thrift Go server endpoint reachable over the network is exposed, with no confidentiality or integrity consequence; the practical exposure is narrowed by network reachability and by whether the deployment accepts Thrift traffic from untrusted clients. CISA KEV does not list this issue and no public exploit code was identified at time of analysis, so exploitation appears to require only a crafted or excessive-volume Thrift message rather than a published attack tool.
Denial of service in the Java bindings of Apache Thrift (all versions before 0.25.0) allows an accepted protocol peer to exhaust server resources by triggering unbounded allocation while Thrift messages are received and parsed. Per the assessed CVSS vector (PR:L), the attacker must already be an authenticated or otherwise accepted client of the Thrift service rather than an anonymous internet actor, which materially narrows exposure for deployments that only accept connections from trusted peers. The impact ceiling is availability loss only - no data disclosure, integrity impact, or code execution is declared - and no public exploit code or CISA KEV entry is associated with this CVE at time of analysis; the vendor-released fix is version 0.25.0.
Remote, unauthenticated attackers can crash applications built against Apache Thrift's c_glib (C/GLib) language bindings before version 0.25.0 by supplying crafted Thrift protocol input that triggers access of an uninitialized pointer (CWE-824), degrading availability with no confidentiality or integrity impact. The flaw carries a CVSS 4.0 score of 8.7 (assessed as CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), and only deployments that use the c_glib binding and expose a Thrift endpoint to an attacker-reachable network are affected - services using Java, Python, Go or other bindings are not exposed to this particular defect. No public exploit code has been identified at time of analysis and there is no indication of confirmed active exploitation (CISA KEV); a vendor-released patch, version 0.25.0, is available.
Unauthenticated, network-reachable denial of service in Apache Thrift's PHP bindings before 0.25.0 lets attackers crash a Thrift service by sending crafted serialized messages that trigger a stack-based buffer overflow during protocol parsing. The vendor-supplied CVSS 4.0 score of 8.7 reflects high availability impact with no confidentiality or integrity impact (VC:N/VI:N/VA:H) and no privileges or user interaction required (PR:N/UI:N), and the assessed CVSS 3.1 vector agrees (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H). No public exploit code or active exploitation has been identified at time of analysis, and the vendor scope bounds the consequence to service crash/denial of service rather than data disclosure or code execution.
Stack exhaustion in Apache Thrift before 0.25.0 allows remote, unauthenticated attackers to crash processes that deserialize attacker-controlled Thrift messages, because the protocol skip routine in several language bindings fails to apply the binding's recursion limit when skipping unknown fields. The affected bindings are the Python C++ accelerator (the pure-Python protocols are not affected), the PHP library and its thrift_protocol extension, and the Perl, Lua, Smalltalk and OCaml libraries; the CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) confirms the bug is reachable over the network with no privileges or user interaction, but the impact metrics (VC:N/VI:N/VA:H) restrict the consequence to availability loss. There is no code execution or data exposure, no public exploit code and no confirmed active exploitation at time of analysis, and Apache has released version 0.25.0 which restores the recursion limit.
Denial of service in Apache Thrift's c_glib (C/GLib) language bindings before 0.25.0, where a crafted or malformed message reaching the deserialization/parsing path triggers a NULL pointer dereference and uninitialized-variable use that crashes the process. The issue is remotely reachable and unauthenticated (CVSS:4.0 vector AV:N/AC:L/AT:N/PR:N/UI:N with availability-high impact only), so any network-exposed Thrift service built on the c_glib binding is at risk of abrupt termination; confidentiality and integrity are unaffected. Only the c_glib binding is implicated - other Thrift bindings are not affected - and no public exploit code has been identified at time of analysis, with the vendor shipping a fix in 0.25.0.
Heap-based memory corruption in Apache Thrift versions before 0.25.0 lets unauthenticated remote attackers who can send Thrift protocol messages to a parsing service trigger an integer-overflow-driven undersized heap allocation followed by an out-of-bounds write, resulting in a crash (denial of service) or potentially attacker-controlled memory corruption with high confidentiality, integrity, and availability impact. The affected surface is any service that deserializes untrusted Thrift traffic; the CVSS v4.0 score of 9.2 reflects network reachability and no required privileges or user interaction, while the AC:H and AT:P metrics (mirrored by the assessed CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) indicate that a successful exploit depends on crafting malformed messages that reliably hit the overflow condition and on runtime factors such as heap layout, memory limits, and the specific protocol/transport in use. No public exploit code or confirmed active exploitation was identified at time of analysis, but the framework's broad embedding in RPC and serialization pipelines makes prompt upgrade to 0.25.0 the clear priority. Services that never parse Thrift input from untrusted or remote peers are not reachable through this vector.
Denial of service in Apache Thrift's Go bindings (all versions before 0.25.0) allows an unauthenticated remote peer to crash an entire Thrift-serving process by sending a single crafted frame over the TFramedTransport or THeaderTransport. A frame that yields no payload bytes causes the transport to recurse into Read rather than loop, so a peer can drive unbounded recursion with only 4 bytes (declared frame size of zero) or 18 bytes (a header block that fills the frame) until the Go stack limit is hit; the resulting runtime fatal error is not catchable by recover() and kills the process. The impact is availability-only - no confidentiality or integrity effect - and no public exploit code has been identified at time of analysis, though exploitation needs only network reachability to the Thrift listener with no authentication or user interaction (CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/.../VA:H).
Memory exhaustion in Apache Thrift's Node.js and D language WebSocket server transports (all versions before 0.25.0) lets unauthenticated remote attackers commit 513 MiB on a Node.js server, or up to 2 GiB on the D transport, by sending a single ~14-byte frame that merely declares a huge payload length. The transport reads the length out of the WebSocket frame header and allocates that many bytes immediately, before the payload has actually arrived, so an extremely small request causes disproportionate memory growth; in the Node.js case the connection is left open afterwards, allowing the same frame to be resent repeatedly until the service is exhausted or killed. Impact is limited to availability (CVSS 4.0 8.7, CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), no authentication or user interaction is required, and no public exploit code was identified at time of analysis. Affected deployments are those exposing the Thrift WebSocket server transport from the Node.js or D bindings; other Thrift transports and language bindings are out of scope.
Denial of service in Apache Thrift's c_glib (C/GLib) language bindings, affecting all versions before 0.25.0, where a crafted or malformed Thrift message can drive the decoder into an infinite loop with an unreachable exit condition (CWE-835). The issue is remotely reachable and requires no authentication per the published CVSS 4.0 vector (PR:N), though the AT:P attack-requirements flag and our independent CVSS 3.1 assessment (AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H) both indicate a specific input condition must be satisfied rather than arbitrary traffic. Impact is confined to availability - a hung thread, pinned CPU, or resource exhaustion that can stall or crash the service - with no data exposure, modification, or code execution; only applications that compile and use the c_glib bindings are affected, and no public exploit code has been identified at time of analysis. Upgrading to 0.25.0 removes the condition.
Denial of service in the PHP bindings of Apache Thrift before 0.25.0 allows unauthenticated remote attackers to exhaust process stack space and crash the parsing worker by supplying deeply nested or self-referential serialized Thrift messages. The flaw is an uncontrolled recursion (CWE-674) in the deserialization path, rated 8.2 High under CVSS 4.0 (AV:N/AC:L/AT:P/PR:N/UI:N/VA:H, with no confidentiality or integrity impact) and 8.2-equivalent High under the assessed CVSS 3.1 vector (A:H only), confirming that impact is confined to availability. Exploitation is not unconditional: the CVSS 4.0 AT:P attack-requirement flag reflects that the target service must actually accept and deserialize attacker-controllable Thrift payloads through the PHP bindings, so internal services processing only trusted, bounded data are not realistically exposed. There is no public exploit code and no confirmed active exploitation at time of analysis, and a vendor-released fix is available in Apache Thrift 0.25.0.
Denial of service in the Apache Thrift Perl bindings affects all releases before 0.25.0, allowing unauthenticated remote attackers to exhaust CPU or memory resources on services that deserialize attacker-controlled Thrift messages through the Perl language runtime. Only deployments using the Perl bindings are exposed; services built on the Java, Python, C++, or Go bindings are not affected by this specific flaw, and no public exploit code was identified at time of analysis, nor is there any CISA KEV confirmation of active exploitation. Impact is availability-only (no confidentiality or integrity loss), the vendor-released fix is Apache Thrift 0.25.0, and exploitation depends on the malicious input actually reaching the vulnerable parsing routine (the CVSS 4.0 AT:P / assessed AC:H condition).
Services that parse attacker-supplied input through Apache Thrift's Perl bindings before version 0.25.0 can be driven into an uncaught exception, crashing the hosting process or thread and causing a denial of service. The flaw is network-reachable and requires no authentication or user interaction (CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N, score 8.2), but its impact is confined to availability (VA:H) with no confidentiality or integrity effect, and the CVSS 4.0 AT:P metric indicates a specific precondition - the attacker's input must actually reach the vulnerable Perl deserialization/handler path. No public exploit code or confirmed active exploitation was identified at time of analysis, and the issue is resolved by the vendor's 0.25.0 release.
Uncaught exception handling in the Apache Thrift Ruby bindings lets unauthenticated remote attackers crash network-reachable Thrift RPC services running any version before 0.25.0. Per the assessed vector (AV:N/AC:L/PR:N/UI:N), no credentials, user interaction, or special configuration are required: any reachable Thrift Ruby service that parses attacker-supplied protocol messages can be knocked offline, though impact is limited to availability with no confidentiality or integrity loss. The flaw carries a CVSS 4.0 score of 8.7 (High) and an assessed CVSS 3.1 of 7.5, and no public exploit identified at time of analysis; exposure is confined to deployments using the Ruby language bindings rather than Thrift bindings for other languages.
Inefficient algorithmic complexity (CWE-407) in Apache Thrift's Lua bindings prior to version 0.25.0 allows remote, unauthenticated attackers to exhaust CPU and cause denial of service by supplying crafted input that the Lua binding parses. Only deployments that specifically use the Thrift Lua language binding and expose it to attacker-influenced data are affected; applications using other Thrift language bindings (Java, Python, C++, Go, etc.) are not impacted. The impact is limited to availability - no confidentiality or integrity loss is indicated by the assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 8.7), and no public exploit code or confirmed active exploitation was identified at time of analysis.
Denial of service in Apache Thrift's JavaME bindings (versions before 0.25.0) allows unauthenticated remote attackers to exhaust server resources by sending crafted Thrift protocol input, causing service outages. The flaw is CWE-770 (uncontrolled resource allocation) and is limited to availability impact; there is no confidentiality or integrity exposure. No public exploit code or active exploitation has been identified at time of analysis, and upgrading to 0.25.0 resolves the issue.
Unbounded resource allocation in the Ruby bindings of Apache Thrift (versions before 0.25.0) lets unauthenticated remote clients exhaust server memory or CPU by sending Thrift messages whose declared structure or container sizes trigger excessive allocation while the service deserializes them. Only network-reachable services that actually accept and parse untrusted Thrift payloads through the Ruby bindings are exposed, and the impact is confined to availability, with no data disclosure or modification (C:N/I:N/A:H). The Apache Software Foundation has released 0.25.0 as the fix; no public exploit code or confirmed active exploitation was identified at time of analysis, and the vendor rates this 8.2 (High) under CVSS 4.0, while our independent assessment also treats it as High severity but notes a higher attack complexity (AC:H in v3.1 terms) because the attacker must reach a service that parses untrusted Thrift messages.
Denial of service in the Lua language bindings of Apache Thrift before 0.25.0 allows unauthenticated remote attackers to exhaust server resources by sending crafted Thrift messages that trigger uncontrolled allocation or inefficient algorithmic paths. The issue is limited to deployments that actively use the Lua bindings; other language bindings are unaffected. At time of analysis there is no confirmed active exploitation (not in CISA KEV) and no public exploit code identified, and the impact is confined to availability-no data disclosure or code execution.
Denial of service in Apache Thrift Python bindings before 0.25.0 allows unauthenticated remote attackers to hang the service by sending crafted Thrift messages that drive the parser into an infinite loop (CWE-835). Exploitation is network-based but requires a specific condition, such as a particular protocol/transport or malformed message structure, to trigger the loop (AT:P / AC:H). The impact is limited to availability-no data disclosure or code execution-and only services exposing a Thrift endpoint that processes untrusted input using the Python bindings are affected; no public exploit code has been identified at time of analysis.
Denial of service in the Apache Thrift PHP bindings before version 0.25.0 allows unauthenticated remote attackers to exhaust server resources by sending crafted Thrift protocol messages that trigger inefficient algorithmic complexity (CWE-407). The vulnerability affects only applications that use the PHP bindings to deserialize untrusted Thrift input; other language bindings are unaffected. No public exploit code has been identified at the time of analysis, and the CVSS 4.0 AT:P metric indicates a specific attack precondition must be met, so exploitation is not guaranteed against every deployment.
Denial of service in Apache Thrift's Go bindings (versions before 0.25.0) lets unauthenticated remote attackers exhaust memory or CPU by sending highly compressed payloads over a compressed transport, so a tiny request expands into a disproportionately large in-memory buffer (CWE-409 data amplification / decompression bomb). Exploitation is conditional: per the vendor's CVSS 4.0 score the AT:P metric applies, meaning the affected service must actually accept attacker-supplied compressed data (for example a zlib-backed transport carrying untrusted input) - deployments of the Go bindings that do not parse compressed payloads from external sources are not exposed. Impact is availability-only (service crash, hang, or memory exhaustion) with no code execution or data disclosure; no public exploit code and no confirmed active exploitation were identified at time of analysis, and our independent assessment uses a 3.1 vector of AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H reflecting that precondition.
Denial of service in Apache Thrift's Python bindings before 0.25.0 arises from improper handling of highly compressed data (CWE-409), letting a remote, unauthenticated attacker send a small compressed Thrift payload that expands dramatically during parsing and exhausts server memory or CPU. Exploitation requires a service that accepts externally supplied Thrift data and decompresses or size-expands it, and the impact is confined to availability with no data disclosure or code execution. No public exploit code has been identified at time of analysis, and upgrading to 0.25.0 eliminates the vulnerability.
Denial of service in the D-language binding of Apache Thrift (thrift.server.nonblocking.TNonblockingServer) allows unauthenticated remote attackers to crash the server by sending a crafted or malformed message that provokes an uncaught exception and improper resource shutdown. Only deployments built with the D binding at versions before 0.25.0 and specifically using TNonblockingServer are affected, and the impact is limited to availability with no data exposure or modification. No public exploit code has been identified at time of analysis, and the vendor has released version 0.25.0 to fix the issue.
Unauthenticated remote attackers can crash applications that use the Apache Thrift PHP bindings prior to version 0.25.0 by supplying crafted Thrift protocol messages that trigger a NULL pointer dereference (CWE-476). The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) indicates the flaw is remotely reachable with low complexity and requires no authentication or user interaction, but the impact profile is availability-only (VC:N/VI:N/VA:H) - there is no confidentiality or integrity exposure, so the 8.7 score reflects a pure denial-of-service outcome rather than code execution. Exploitation is conditional on the target PHP service actually accepting and deserializing attacker-controlled Thrift input, and no public exploit code has been identified at time of analysis. A vendor patch is available in Apache Thrift 0.25.0, which per the advisory fixes the issue.
Denial of service in Apache Thrift deployments that use the D language bindings before version 0.25.0, where malformed input reaching the service endpoint triggers an uncaught exception, an infinite loop with an unreachable exit condition, and an integer underflow that can crash or hang the service. The assessed impact is availability-only (CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H; vendor CVSS 4.0 base 8.7), meaning unauthenticated remote attackers who can reach a D-bindings Thrift service need no credentials, user interaction, or non-default configuration to cause disruption. Exposure is narrow because only services compiled against the D bindings are affected - Java, Python, C++, Go and other language binding deployments are not - and no public exploit code has been identified at time of analysis.
Denial of service and limited integrity tampering in Apache Thrift before 0.25.0 stem from a combination of an infinite loop (CWE-835) and prototype pollution in the Node.js bindings when the TJSONProtocol deserializer parses crafted JSON. Any application exposing a Thrift service built on the Node.js library with TJSONProtocol enabled on an untrusted, attacker-reachable input path can be driven into an unreachable-exit loop that hangs the process, with secondary risk of object prototype attribute manipulation altering application state; the vulnerability is reachable unauthenticated and without user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N, availability High, integrity Low) and the vendor rates it 8.7. No public exploit code has been identified at time of analysis and the issue is not recorded as actively exploited, though the affected product family and the low attack complexity make it a realistic target for opportunistic scanning. Risk is bounded by deployment: services using TBinaryProtocol, TCompactProtocol or non-Node.js Thrift bindings are not affected by this vector.
Integer underflow in Apache Thrift's C++ THeaderTransport can wrap a length or offset calculation and produce an out-of-bounds write, allowing a network attacker to crash or destabilize services that parse THeader-framed messages. The exposure is narrow: the library must be compiled as a 32-bit binary and must actually use THeaderTransport, while 64-bit builds and services relying on other transports are not affected, so the realistic outcome is denial of service rather than code execution or data disclosure. Affected releases are Apache Thrift before 0.25.0; no public exploit code has been identified at time of analysis, and the vendor's own scoring reflects availability-only impact (VA:H with no confidentiality or integrity effect).
Memory exhaustion in Apache Thrift before 0.25.0 lets unauthenticated remote attackers crash services that deserialize attacker-controlled Thrift messages, and the flaw is present across the Go, netstd, OCaml, Erlang, JavaME, Rust, C++, Java, Kotlin, and D language bindings. The supplied CVSS 4.0 vector (8.7 High) and the independent assessment (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) agree that impact is availability-only: no confidentiality or integrity loss, and no authentication, user interaction, or special configuration is required beyond a reachable endpoint that accepts untrusted Thrift input. No public exploit code was identified at time of analysis and the issue is not confirmed as actively exploited (CISA KEV); the vendor-released fix is version 0.25.0.
Denial of service in Apache Thrift's Erlang bindings affects all releases before 0.25.0, where unauthenticated remote attackers who can reach a Thrift service that parses untrusted serialized input can send deeply nested or otherwise resource-heavy messages that the Erlang deserialization code processes without recursion-depth or allocation limits. The result is uncontrolled recursion and unbounded resource consumption (CWE-674), leading to service crash or hang - availability impact only, with no confidentiality or integrity loss confirmed. Exploitation requires the specific precondition that the target actually parses the attacker-supplied payload (CVSS 4.0 AT:P), and the flaw is confined to the Erlang bindings rather than all Thrift language bindings, so this is a moderate-priority availability issue rather than a top-tier emergency; no public exploit code has been identified at time of analysis, and the vendor-released fix is Apache Thrift 0.25.0.
Denial of service in the Lua language bindings of Apache Thrift allows unauthenticated remote attackers to exhaust CPU resources by supplying pathologically crafted input to a regular-expression or parsing code path in releases before 0.25.0, consistent with CWE-1333 (inefficient regular expression complexity). The CVSS 4.0 vector scores 8.2 with AT:P, indicating that a specific attack prerequisite must be met: the deployment must actually use the Lua bindings and attacker-controlled data must reach the vulnerable parsing path, so exploitation is not fully attacker-controlled. The vendor-released fix is Apache Thrift 0.25.0; no public exploit code was identified at time of analysis and there is no confirmed active exploitation (no CISA KEV listing), with the effective risk concentrated in services that parse untrusted input through the Lua binding.
Denial of service in the Erlang language bindings of Apache Thrift before 0.25.0 allows remote attackers to exhaust server resources through unbounded allocation, degrading or crashing the affected service. The flaw is CWE-770 (Allocation of Resources Without Limits or Throttling) and carries a CVSS v4.0 base score of 8.2; our independent assessment scores it CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H, reflecting a high-availability-only impact that requires a specific crafted message structure (AT:P) rather than arbitrary traffic. Only deployments running a Thrift server compiled with the Erlang bindings and exposed to attacker-reachable network traffic are affected; users of the C++, Java, Python, Go and other bindings are not impacted, and no public exploit code was identified at time of analysis.
An uncaught exception (CWE-248) in Apache Thrift's PHP language bindings before 0.25.0 allows unauthenticated remote attackers to terminate PHP processes that accept arbitrary Thrift protocol input, producing a denial of service with no confidentiality or integrity impact. The assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) means no privileges or user interaction are required against a default deployment that exposes a vulnerable PHP-based Thrift endpoint to untrusted network traffic; the practical prerequisite is that the target actually uses the PHP bindings rather than another language binding. No public exploit code and no confirmed active exploitation were identified at time of analysis, and exploitation potential is bounded to service availability - this is a genuine but limited availability risk rather than a data-breach emergency.
Denial of service in the Apache Thrift PHP bindings before 0.25.0 allows unauthenticated remote attackers who can reach a Thrift service built on those bindings to exhaust server resources via unbounded allocation. The flaw is CWE-770 (allocation of resources without limits or throttling), triggered when the PHP binding processes attacker-controllable message sizes or collections without a cap; impact is limited to availability (VA:H; VC:N/VI:N), meaning no data disclosure or code execution. There is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV), so risk is highest for externally reachable Thrift endpoints that accept untrusted clients. Vendor-released patch: 0.25.0.
Unbounded resource allocation in the Node.js bindings of Apache Thrift (all versions before 0.25.0) allows remote, unauthenticated attackers to exhaust memory and crash an exposed Thrift service by sending a crafted message whose declared quantity/size field is not validated before allocation. Impact is limited to availability: no confidentiality or integrity effect, and no code execution is achievable through this path. Exploitation requires a Node.js binding deployment that actually parses untrusted client input (the assessed AT:P condition), and because only the Node.js bindings below 0.25.0 are affected, deployments using other language bindings or newer versions are not exposed; there is no public exploit code identified at time of analysis and the flaw is not listed as confirmed actively exploited (CISA KEV).
Uncontrolled recursion in Apache Thrift's c_glib (C/GLib) bindings causes stack exhaustion and process crash when a crafted, deeply nested message is deserialized from an untrusted source. Only applications built against the c_glib bindings at versions before 0.25.0 are affected; deployments using the Java, Python, C++ or other language bindings are not impacted by this specific issue. The flaw is availability-only - no confidentiality or integrity loss - and is reachable over the network without authentication (CVSS:4.0 PR:N, AT:P), though exploitation depends on the recursive parsing path being exposed to attacker-controlled input; no public exploit code or confirmed active exploitation was identified at time of analysis.
Repeated, attacker-triggered exceptional conditions in the Apache Thrift Java bindings can leak server-side resources and degrade or exhaust a Thrift RPC service running any version before 0.25.0. The issue is remotely reachable without authentication (CVSS PR:N) and needs no user interaction, but the assessed impact is availability only - there is no confirmed confidentiality or integrity effect, so this is a denial-of-service exposure rather than a data-compromise issue. A CVSS 4.0 attack-requirement flag (AT:P) indicates a specific precondition must be met to drive the vulnerable error path, meaning not every request triggers the leak; the precise condition is not specified in the public advisory text, and no public exploit identified at time of analysis. Deployments not using the Java bindings, or already on 0.25.0 or later, are unaffected.
Uncontrolled recursion in the Dart and Java ME bindings of Apache Thrift before 0.25.0 lets a remote, unauthenticated attacker crash or hang a service by sending a Thrift message containing deeply nested or self-referential structures that exhaust the parser's stack. Impact is availability-only (no confidentiality or integrity effect per the assessed CVSS:3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), and the vulnerable surface is confined to deployments that deserialize untrusted data using the Dart or Java ME bindings, so most Thrift users on Java SE, C++, Python, or Go are not exposed. No public exploit code or confirmed active exploitation was identified at time of analysis; the CVSS 4.0 base score of 8.7 should be read alongside the narrow binding-specific exposure, which makes real-world priority moderate rather than critical.
Denial of service in Apache Thrift before 0.25.0 allows unauthenticated remote attackers to crash or exhaust services running affected language bindings by sending malformed Thrift protocol data. The flaw combines improper length-parameter handling with excessive memory allocation, inefficient algorithmic complexity, uncaught exceptions, and insecure default initialization across the Python, Ruby, Erlang, Lua, Dart, JavaME, Perl, PHP, and D bindings. It is availability-only: no code execution, data disclosure, or data tampering is known from this issue. No public exploit code or confirmed active exploitation was identified at time of analysis; upgrading to 0.25.0 resolves it.
Heap-based buffer overflow in the C++ THeaderTransport of Apache Thrift before 0.25.0 lets a remote, unauthenticated attacker corrupt heap memory when an application enables the non-default ZLIB transform for outgoing frames and poorly compressible, peer-influenced data expands during compression. The copy into the write buffer happens without a bounds check, so oversized input overflows the heap allocation and, for large frames, also reads past the end of the transform buffer; impact scales with frame size and reliable code execution versus a crash depends on heap layout. No public exploit code has been identified at time of analysis, and because exploitation requires the ZLIB write transform precondition (without it the vulnerable copy path is never reached), this is a credible high-priority issue rather than an automatic emergency.
Denial of service in the Apache Thrift PHP bindings before version 0.25.0 lets remote, unauthenticated attackers exhaust CPU and memory on a Thrift-serving PHP application by sending a crafted Thrift message whose declared quantity is never validated. Per the assessed CVSS:3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, vendor CVSS 4.0 base 8.7), the weakness is availability-only: there is no code execution, data exposure, or integrity impact, and only deployments that use the PHP bindings to parse untrusted Thrift input over the network are exposed. No public exploit code or confirmed active exploitation (no CISA KEV listing) was identified at time of analysis, and no EPSS score was supplied; non-PHP Thrift bindings are out of scope for this issue.
Denial of service in Apache Thrift's Python bindings (all versions before 0.25.0) allows remote, unauthenticated clients to force unbounded memory allocation by sending crafted messages that declare oversized containers or strings, crashing or hanging the affected service. The flaw pairs a missing resource limit with an insecure default configuration in which the bindings apply no read or container size cap unless the application explicitly sets one, so any network-reachable Thrift service that accepts untrusted traffic while running on those defaults is exposed. Impact is confined to availability with no confidentiality or integrity effect, and the CVSS 4.0 AT:P component reflects that a specific, not fully attacker-controlled deployment condition must be met; no public exploit code has been identified at time of analysis and the issue is not in CISA KEV.
Remote denial of service against Apache Thrift C++ deployments that use the THeaderProtocol is achievable by sending a crafted frame header to a network-reachable Thrift endpoint, causing a stack-based buffer overflow that crashes the service; the flaw combines CWE-121 with an incorrect bitwise shift of an integer in the same header-parsing code path. Every Apache Thrift release before 0.25.0 ships the vulnerable C++ implementation, although only services that actually use the THeaderProtocol transport are exposed - services built against other Thrift protocols or transports are not affected by this specific code path. The CVSS 4.0 base score is 8.7 on a fully unauthenticated, network-reachable vector with availability-only impact (VC:N/VI:N/VA:H), and no public exploit code or confirmed active exploitation has been identified at time of analysis.
Memory exhaustion in Apache Thrift's THeaderTransport affects all versions before 0.25.0, allowing remote attackers to cause a denial of service. Per the CVSS vector (AV:N/AC:L/PR:N/UI:N), exploitation is unauthenticated and requires no user interaction: an attacker can send crafted messages to a Thrift endpoint that uses THeaderTransport, triggering unreleased memory allocations that accumulate and eventually exhaust server resources. The flaw is rated CVSS 8.7 (4.0) with availability-only impact (VC:N/VI:N/VA:H); no public exploit code has been identified at the time of analysis.
Denial of service in Apache Thrift's Dart bindings (all versions before 0.25.0) lets an unauthenticated remote attacker crash or hang a service by sending a Thrift message whose length or size field declares an excessive allocation. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N, VA:H, score 8.7) confirms the flaw is remotely reachable without authentication or user interaction, but impact is confined to availability - confidentiality and integrity are explicitly rated N, with no data exposure or code execution described in any source. Only deployments that deserialize attacker-supplied Thrift traffic through the Dart bindings are affected, and no public exploit identified at time of analysis.
Denial of service in the Apache Thrift Java bindings before 0.25.0 allows remote, unauthenticated attackers to crash or exhaust resources on a service that deserializes attacker-controlled Thrift messages, because exceptional conditions on the message-handling path are not handled correctly and resource allocation is not bounded or throttled. Only deployments running affected Thrift Java server code on a network-reachable endpoint are at risk; impact is confined to availability (service crash / resource exhaustion) with no loss of confidentiality or integrity, and a specific precondition must hold - the crafted input must reach the vulnerable exception-handling or allocation path rather than any arbitrary request. There is no public exploit identified at time of analysis, and no confirmed active exploitation (CISA KEV); vendor-released patch: 0.25.0.
Denial of service in Apache Thrift's Lua language bindings (all versions before 0.25.0) allows unauthenticated remote attackers to drive unbounded resource allocation by sending protocol messages whose declared length parameter is inconsistent with the actual data, abusing a missing allocation limit (CWE-770). Per the vendor vector (PR:N/UI:N) no credentials or user interaction are required; impact is confined to availability (AV:N/AC:L/PR:N/UI:N with A:H, and no confidentiality or integrity effect), meaning memory or CPU exhaustion and likely process termination rather than data exposure or modification. Only deployments that expose a Thrift service implemented with the Lua bindings are in scope, so services built on Thrift's C++, Java, Python, Go and other bindings are not affected by this specific issue; no public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV, and no EPSS score was supplied for this analysis.
StartTLS handling in 389-ds-base does not discard plaintext bytes buffered before the TLS upgrade, allowing an on-path attacker to inject a crafted LDAP message whose messageID collides with a client's pending bind and causes the client to treat a failed authentication as successful. Red Hat Directory Server 11, 12, and 13 and Red Hat Enterprise Linux 6, 7, 8, 9, and 10 deployments using 389-ds-base with StartTLS are affected. Exploitation requires an on-path network position and timing control during StartTLS negotiation, so the real-world bar is higher than the reported 9.0 base score; no public exploit identified at time of analysis.
Denial of service in 389-ds-base (the LDAP engine shipped with Red Hat Directory Server 11/12/13 and Red Hat Enterprise Linux 6 through 10) lets an unauthenticated remote attacker stall the server's worker-thread pool by sending a complete LDAP operation followed by the opening bytes of an incomplete LDAPMessage on the same connection. The server then hands the connection to a second worker thread before the first worker's result is flushed; the second worker blocks on the connection mutex until nsslapd-ioblocktimeout, so the finished operation's response is never delivered. Repeating this over a handful of connections proportional to the configured worker-thread count exhausts the entire pool under default configuration, denying LDAP service to anonymous and authenticated clients over both plaintext and TLS for as long as the attacker holds the connections; no public exploit code has been identified at time of analysis, and no EPSS or KEV signal accompanies the CVE, though the availability-only impact (CVSS 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) is genuine for any internet- or broad-network-reachable directory server.
Memory-exhaustion denial of service in FasterXML jackson-dataformats-binary affects the Smile binary parser on 2.16.0-and-later releases, where SmileParser buffers an entire JSON object property name in memory through an unconstrained _growArrayTo() call inside _handleLongFieldName() and never calls StreamReadConstraints.validateNameLength(), so the configured maxNameLength is silently ignored for this format. Any remote, unauthenticated attacker whose bytes reach SmileFactory parsing - directly or through an ObjectMapper configured with the Smile module - can embed a single unbounded property name and force heap exhaustion, because maxDocumentLength is also disabled by default (CVSS 3.1: 7.5, AV:N/AC:L/PR:N/UI:N, availability-only impact), leaving upload capacity and available heap as the only practical limits. No public exploit identified at time of analysis, and applications that parse only standard JSON are unaffected since jackson-core's JSON parsers enforce maxNameLength incrementally during name decoding.
Memory-exhaustion denial of service in the FasterXML jackson-dataformats-binary CBOR parser allows an unauthenticated remote attacker to force unbounded heap allocation by submitting a CBOR document containing a single property name of arbitrary length; the parser buffers the entire name in memory before returning it because maxNameLength is never validated for this binary format. The defect affects jackson-dataformats-binary running against jackson-core 2.16.0 or later (releases before 2.16.0 never contained the constraint that is left unenforced), and is reachable under default configuration because StreamReadConstraints.maxDocumentLength is disabled by default, leaving no built-in bound on the name. Per the assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5) there is no confidentiality or integrity impact, and the practical damage ceiling is set by the attacker's upload capacity versus the victim's available heap; no public exploit code was identified at time of analysis, and exploitation requires only that attacker-controlled bytes actually reach CBORFactory or an ObjectMapper configured with the CBOR module.
Denial of service in Apache HTTP Server releases before 2.4.69, where the mod_xml2enc filter dereferences a NULL pointer when a proxied response declares a charset whose conversion partially succeeds and then fails, crashing the handling child process. Per the assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L), the crash is reachable without credentials over the network, but exploitation is gated by a trust boundary: the request path must run proxied backend responses through mod_xml2enc (in practice mod_proxy_html content rewriting), and the attacker must control or have compromised that upstream backend server - ordinary external clients cannot directly trigger it. Impact is limited to availability (worker/child process termination with no confidentiality or integrity effect), and no public exploit code, KEV listing, or EPSS score was provided at time of analysis, so this is best treated as a low-to-moderate priority hardening item for reverse-proxy deployments that transform untrusted upstream content.
An integer overflow in the mod_dav_fs module of Apache HTTP Server through 2.4.68 allows an authenticated WebDAV client with write access to crash worker processes and persistently corrupt a directory's property database by sending PROPPATCH requests that declare a large number of XML namespaces. The flaw is a CWE-190 integer overflow; the assessed vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H) confirms the attacker must be authenticated with write permissions, and impact is limited to denial of service and property database integrity, with no code execution, privilege escalation, or data disclosure. No CVSS score, EPSS probability, KEV listing, or public exploit code is present in the provided data, so there is no confirmed active exploitation and no public exploit identified at time of analysis.
Concurrent Digest authentication requests against Apache HTTP Server before 2.4.69 can corrupt authentication state via a use-after-free in the mod_auth_digest module, yielding low integrity and availability impact with no confidentiality impact (per the assessed vector AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L). Unauthenticated remote clients can reach the flaw, but exploitation is gated by two non-default preconditions: AuthDigestNcCheck must be enabled or AuthDigestNonceLifetime set to 0, and the attacker must win a timing-dependent race by sending concurrent Digest requests - serial requests will not reliably trigger it. There is no public exploit identified at time of analysis, no EPSS score, no CISA KEV entry, and no vendor-supplied CVSS, so the sole source is the Apache advisory; the fix is version 2.4.69.
Authentication bypass in the mod_auth_digest module of Apache HTTP Server 2.4.x allows a man-in-the-middle attacker to capture a victim's HTTP Digest authentication credentials and replay them to impersonate that user against the server. Exploitation is conditional: the server must have mod_auth_digest enabled and the non-default directive AuthDigestNonceLifetime must be explicitly set to 0, and the attacker must additionally occupy a network interception position to capture the digest exchange and send crafted requests that force garbage collection of the client's shared-memory nonce entry. The assessed vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N) reflects high confidentiality impact but a high attack-complexity and MITM prerequisite; no public exploit code and no confirmed active exploitation were identified at time of analysis, and the source supplied no CVSS score or EPSS estimate.
Apache HTTP Server 2.4.0 through 2.4.68 can leak a client's session cookie to an upstream backend server through the mod_session_cookie module when the effective value of the SessionCookieRemove directive changes as a request passes through an internal redirect (for example via mod_rewrite or mod_proxy rewrites). The exposure is unauthenticated from the network perspective (PR:N in both the NVD vector and our independent vector), but it is strictly conditional: it requires httpd to be deployed as a proxy/front end in front of a backend, mod_session_cookie to be loaded, SessionCookieRemove to be configured, and that configuration to differ between the pre- and post-redirect contexts - our assessment therefore rates it AC:H with C:L rather than the NVD's AC:L/C:H, since the consequence is a trust-boundary leak of the cookie to the backend rather than direct confidentiality loss to an external attacker. CISA SSVC records Exploitation: none, and no public exploit code has been identified at time of analysis, so this is a genuine-but-conditional hardening issue rather than an urgent, actively exploited priority.
Inconsistent interpretation of HTTP responses in Apache HTTP Server's mod_proxy_uwsgi module lets a crafted backend uwsgi response that carries a Transfer-Encoding header be parsed differently by Apache than by the backend, enabling HTTP response smuggling and desynchronization between the proxy and downstream clients. Affected deployments are Apache HTTP Server 2.4.30 through 2.4.68 configured as a reverse proxy to a uwsgi backend via mod_proxy_uwsgi; installations that do not load or use mod_proxy_uwsgi are not affected. The assessed vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N) is network-reachable by unauthenticated remote attackers, but exploitation is gated by high complexity because the attacker must control or influence the backend uwsgi response - typically through a malicious or compromised backend application, or a response-header-injection flaw in it - so this is not reachable against a default Apache install. No public exploit code has been identified and there is no indication of confirmed active exploitation (no CISA KEV listing); impact is limited to low confidentiality and low integrity with a scope change, not full remote code execution or denial of service.
Stack-based buffer overflow in the mod_vhost_alias module of Apache HTTP Server through 2.4.68 allows a remote, unauthenticated client to crash the server or potentially execute arbitrary code by sending an HTTP request whose Host header exceeds 8192 bytes. The flaw is not reachable in default deployments: the operator must have configured VirtualDocumentRoot (or VirtualScriptAlias) with a hostname format specifier such as %0 or %1 and must have raised LimitRequestFieldSize above its 8192-byte default, a non-default and uncommon combination that is reflected in the assessed vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. No KEV listing, EPSS score, or public exploit code was available at time of analysis, so there is no public exploit identified at time of analysis; the dominant uncertainty is the absence of any quantitative exploitation signal, while the real-world exploitability is sharply constrained by the required operator-set configuration. Users are advised to upgrade to 2.4.69, which fixes the issue.
Forward proxy deployments of Apache HTTP Server through 2.4.68 that relay FTP traffic can be manipulated by an untrusted FTP server into opening a data connection to an arbitrary third-party host, because mod_proxy_ftp fails to validate the address returned in an FTP PASV reply. Only non-default configurations with forward proxying enabled (ProxyRequests On) and mod_proxy_ftp loaded are affected, and the primary impact is a misdirected outbound data connection rather than compromise of the proxy host itself. No KEV entry, EPSS score, or POC was supplied and no public exploit has been identified at time of analysis, so prioritization signals are limited and authentication requirements are not confirmed from the supplied data.
Improper privilege management in Apache HTTP Server's mod_ssl (versions 2.4.0 through 2.4.68) causes SSLRequire access-control directives that use file-related expressions to be evaluated in a way that can grant or deny access contrary to the server operator's intent, giving a remote attacker a possible means to reach content that the SSLRequire check was meant to protect or, conversely, to disrupt intended authorization. The flaw is not reachable in a default configuration: exploitation requires mod_ssl to be loaded and the operator to have configured access control specifically through the SSLRequire directive using file-related expressions, a non-default, operator-chosen configuration, which is reflected in the assessed vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N (high attack complexity, low confidentiality and integrity impact, no availability impact); authentication requirements for the attacker are not confirmed from available data. There is no CISA KEV listing and no public exploit code identified at time of analysis, and no EPSS score was provided.
An out-of-bounds write in Apache HTTP Server 2.4.0 through 2.4.68 on Windows can corrupt memory when the server processes request paths containing MS-DOS 8.3 short filenames that expand to longer names, giving a remote attacker a route to service disruption (assessed availability impact High) with limited confidentiality and integrity impact. Exploitation is Windows-only and conditional: 8.3 short-name generation must be enabled on the underlying NTFS volume (the historical default unless NtfsDisable8dot3NameCreation has been set) and the crafted path must actually reach the expanding-path code path, which is reflected in the assessed vector's AC:H. Apache published no CVSS score, and the supplied intelligence contains no CISA KEV listing, no public exploit code, and no EPSS probability, so there is no public exploit identified at time of analysis.
Use-after-free in Apache HTTP Server's mod_http2 module (versions 2.4.0 through 2.4.68) allows unauthenticated remote attackers to corrupt memory and crash server worker processes by driving re-entrant access to a shared per-session buffer. The flaw only manifests when mod_http2 is loaded and HTTP/2 is actually enabled (h2 and/or h2c in the Protocols directive), and the trigger requires specific concurrent/streamed HTTP/2 request patterns, so the assessed vector is network-reachable but high complexity (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H) with impact limited to availability. No public exploit code or active exploitation has been identified at time of analysis, and no EPSS score was supplied.
Denial of service in Apache HTTP Server 2.4.0 through 2.4.68 arises from a use-after-free in the mod_rewrite module that is reachable only when a RewriteRule or RewriteCond uses the lookahead variables %{LA-U:...} or %{LA-F:...}, which exercise an internal subrequest code path. An unauthenticated remote attacker who can reach a server configured that way can trigger the memory error and crash request-handling processes, degrading or halting service; the independent assessment rates this CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H, so impact is confined to availability and the high attack complexity combined with the non-default configuration prerequisite substantially limits real-world exploitability. No CVSS score or vector has been published by NVD or the vendor, there is no EPSS probability and no CISA KEV listing, and no public exploit code has been identified at time of analysis.
An out-of-bounds write in Apache HTTP Server's optional mod_charset_lite module (affecting versions 2.4.0 through 2.4.68) can corrupt process memory when character-set translation is configured, potentially crashing the server or enabling limited data disclosure or modification. Exposure is narrow: mod_charset_lite is not loaded in default installations and must be explicitly enabled and bound to a content path via directives such as CharsetSourceEnc, CharsetDefault, or an associated input/output filter, which is why the assessed vector rates attack complexity as high (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L). Independent signals are otherwise sparse - no public exploit code, no CISA KEV listing, and no EPSS score were available - so no public exploit identified at time of analysis, and the practical severity hinges on whether the module is deployed.
Out-of-bounds write in the NVIDIA Virtual GPU Manager (vGPU plugin) lets an unprivileged user inside an assigned guest VM corrupt host-side memory by sending a specially crafted RPC call across the virtualization channel, resulting in privilege escalation, data tampering, and denial of service on the host. Rated CVSS 7.3 (AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H), the bug is only reachable in vGPU/VDI/cloud-GPU deployments where the host runs the vGPU plugin and has at least one guest assigned; it is not a network-facing flaw and does not affect standard bare-metal Linux GPU driver installs, and no public exploit code has been identified at time of analysis. Real-world risk is therefore defined by the attack surface rather than by mass exploitability, since a successful attack requires an attacker to already hold an unprivileged local account inside a hosted guest VM.
Incorrect resource transfer between spheres in the NVIDIA vGPU Virtual GPU Manager for Linux allows a locally positioned, low-privileged attacker to break an internal resource-handling boundary and gain high-integrity impact - code execution, privilege escalation, data tampering, information disclosure, or denial of service on the host running the vGPU Manager. This affects virtualization/vGPU deployments on Linux (the manager component on the hypervisor host), not standard desktop GPU drivers, and the CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.8) confirms the attacker must already hold local low-privileged access to a context served by that manager, such as a guest VM or a local account on the host; there is no network or unauthenticated path. It is a genuine local privilege-escalation class issue rather than a remotely triggerable one, and no public exploit was identified at time of analysis.
An out-of-bounds read in the kernel-mode layer of the NVIDIA vGPU Virtual GPU Manager for Linux lets a local attacker who can already reach the vGPU kernel interface trigger memory reads past the bounds of an allocated buffer, potentially yielding information disclosure, data tampering, privilege escalation, denial of service, or kernel code execution. The flaw is rated CVSS 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning it is only reachable by an authenticated local principal - a low-privileged user or a guest context on the hypervisor - and not by an unauthenticated remote network attacker. Exposure is limited to hosts that actually deploy NVIDIA vGPU on Linux (VDI and cloud-GPU virtualization platforms), where the highest-impact scenario is a multi-tenant deployment in which the over-read crosses tenant isolation boundaries; no public exploit code or CISA KEV entry was identified at time of analysis, so this is a genuine but not emergency-grade issue warranting scheduled patching.
Local privilege escalation, code execution, denial of service, information disclosure, and data tampering are possible in NVIDIA GPU Display Driver for Linux due to a use-after-free in the open-source kernel module's event-delivery path. An authenticated local user with access to NVIDIA GPU device nodes can race asynchronous event delivery against file close (CVSS 7.0, AV:L/AC:H/PR:L/UI:N), though the high attack complexity makes success non-deterministic and typically requires repeated attempts; no public exploit has been identified at time of analysis. Risk is concentrated on Linux hosts using the affected open-source kernel module, particularly multi-tenant vGPU, VDI, and cloud GPU deployments.
Local privilege escalation in the NVIDIA GPU Display Driver for Linux kernel-mode layer allows an already-present local user or code-execution foothold (PR:L) to write to memory that should be read-only because memory permissions are not preserved, potentially achieving code execution and elevated privileges on affected GeForce, RTX/Quadro/NVS, and Tesla systems, including vGPU Guest Driver deployments. Exploitation requires local access and high attack complexity, with no remote or unauthenticated network path; no public exploit was identified at time of analysis and the CVE is not listed in CISA KEV. The vendor-supplied CVSS vector uses AV:P while our independent assessment uses AV:L, so the physical-access requirement should be confirmed against NVIDIA bulletin 5861.
Denial of service and kernel memory disclosure in the NVIDIA GPU Display Driver for Windows and Linux let a local, low-privileged user who already holds an interactive session on the host force the kernel-mode component to dereference an untrusted pointer, crashing the driver or leaking kernel memory. The flaw is scored CVSS 3.1 7.1 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H) - a local-only, low-complexity attack requiring low-privilege authenticated access with no user interaction, delivering high confidentiality and availability impact but no integrity or write primitive, so it cannot by itself be chained into privilege escalation or code execution. No public exploit code has been identified and there is no confirmed active exploitation (no CISA KEV listing); the most exposed deployments are multi-user, VDI, and cloud-GPU hosts where untrusted users share a GPU, since the attacker must first obtain code execution or an interactive session on the GPU host.
Authenticated low-privileged local users can bypass cryptographic signature verification in the kernel-mode layer of the NVIDIA GPU Display Driver for Linux when the system is under memory pressure, leading to data tampering and denial of service. The flaw affects GeForce, RTX/Quadro/NVS, and Tesla driver branches on Linux; no public exploit code has been identified at time of analysis. Our assessment rates this as a genuine but bounded-priority local issue because the attacker must reliably induce a low-memory kernel state at the moment of verification, making exploitation opportunistic rather than dependable.
Local privilege escalation in NVIDIA GPU Display Driver for Windows and Linux can be achieved by an unprivileged local user through the open-source kernel module's DMA-BUF import path, where importing a read-only buffer from another device's DMA-BUF exporter improperly preserves memory access permissions. Successful exploitation can result in code execution, privilege escalation, denial of service, information disclosure, and data tampering, with CVSS 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). No public exploit identified at time of analysis, and no CISA KEV entry is present in the provided data.
Local privilege escalation and kernel-level code execution in the NVIDIA GPU Display Driver for Windows and Linux, where the kernel-mode layer follows an error-handling path that operates on an improperly initialized resource (CWE-908). The flaw is reachable by an authenticated, low-privileged local user (CVSS 3.1: AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.8 HIGH) on any host where the affected driver is installed and loaded, granting full confidentiality, integrity, and availability impact within the kernel-mode driver's scope. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (not in CISA KEV); risk is concentrated on shared multi-tenant GPU hosts such as VDI, cloud GPU instances, and vGPU guests where untrusted local users coexist with the driver, and success may be probabilistic because the attacker must reliably trigger the failing error path.
Local privilege escalation in the NVIDIA GPU Display Driver for Linux (open-source kernel module variant) allows any unprivileged local user with an account on the host to abuse a DMA mapping code path where memory access permissions are not properly preserved, potentially yielding code execution, privilege escalation, denial of service, information disclosure, or data tampering. The vulnerability is rated CVSS 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning exploitation requires only local access, no user interaction, and no elevated privileges to trigger, but it is confined to systems running the open-source kernel module - the proprietary module is not affected. There is no public exploit identified at time of analysis and no CISA KEV listing; risk is concentrated in multi-user, VDI, cloud-GPU, and HPC hosts where untrusted local users share GPU-equipped machines.
Local privilege escalation in the NVIDIA GPU Display Driver's open-source kernel module lets an unprivileged local user trigger a use-after-free in the Resource Server map cleanup path via a missing self-reference guard, yielding code execution, privilege escalation, denial of service, information disclosure and data tampering (CVSS 3.1 7.8, AV:L/AC:L/PR:L/UI:N, CWE-416). Affected are Windows and Linux hosts running the open-source kernel module variant of the driver, spanning GeForce, RTX/Quadro/NVS and Tesla product lines per the published CPEs; exploitation requires only a normal local account and no user interaction, but is strictly local with no network vector. No public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis, and the practical risk is highest in shared or multi-tenant GPU environments (vGPU, VDI, cloud GPU) where gaining kernel-level control of the GPU driver crosses a meaningful tenant boundary.
Local privilege escalation in NVIDIA GPU Display Driver for Linux allows an authenticated local unprivileged user to write to memory that the kernel-mode display driver should keep read-only because permissions are not preserved (CWE-281), potentially causing code execution, privilege escalation, denial of service, information disclosure, or data tampering. The affected CPE branches are GeForce, RTX/Quadro/NVS, Tesla, and Guest Driver on Linux, with CVSS 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) indicating high impact after local access. No public exploit identified at time of analysis, and the practical risk is a genuine but not emergency-grade local privilege-escalation issue, most meaningful in shared or multi-tenant GPU environments.
Local privilege escalation and potential code execution in NVIDIA GPU Display Driver for Windows and Linux arise from a use-after-free (CWE-416) reachable by a low-privileged local user who can issue a crafted sequence of driver commands. The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) rates confidentiality, integrity, and availability impact as high, with the greatest risk in shared or virtualized GPU deployments where guest-driver or virtual GPU manager isolation may be broken. No public exploit code or confirmed active exploitation is identified in the available data, and EPSS is not provided; exploitation requires local access and construction of the specific command sequence.
An out-of-bounds read in the kernel-mode layer of NVIDIA GPU Display Driver on Windows and Linux allows a local, authenticated unprivileged user to potentially achieve code execution, privilege escalation, denial of service, information disclosure, or data tampering. Affected products include GeForce, RTX/Quadro/NVS, and Tesla GPUs, as well as Guest Driver and vGPU Manager deployments. With a CVSS score of 7.8, the vulnerability requires local access and low privileges (CVSS vector AV:L/AC:L/PR:L/UI:N), making it primarily a risk in multi-user or shared-GPU environments; no public exploit has been identified at time of analysis, and patched driver branches are available in NVIDIA security bulletin 5861.