huzaifas-sidhpurwala/security-commit huggingface dataset:
CVE-2025-2559: org.keycloak/keycloak-services: JWT Token Cache Exhaustion Leading to Denial of Service (DoS) in Keycloak
Component: org.keycloak/keycloak-services
Severity: Moderate
CWE: CWE-770 (Allocation of Resources Without Limits or Throttling)
CVSS v3: 4.9 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H)
Public date: 2025-03-20T00:00:00+00:00

A flaw was found in Keycloak. When the configuration uses JWT tokens for authentication, the tokens are cached until expiration. If a client uses JWT tokens with an excessively long expiration time, for example, 24 or 48 hours, the cache can grow indefinitely, leading to an OutOfMemoryError. This issue could result in a denial of service condition, preventing legitimate users from accessing the system.


Affected upstream versions: 23.0.0 < 26.0.11, 26.1.0 < 26.1.5
Fixed upstream versions: 26.0-12, 26.0-13, 26.0.11, 26.0.11-2, 26.1.5
Upstream repository: https://github.com/keycloak/keycloak
Upstream fix commit: a10c8119d4452b866b90a9019b2cc159919276ca
CVE-2025-26434: libxml2: Libxml2 out of bounds read
Component: libxml2
Severity: Moderate
CWE: CWE-120 (Buffer Copy without Checking Size of Input ('Classic Buffer Overflow'))
CVSS v3: 5.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N)
Public date: 2025-09-05T16:10:02.497000+00:00

An out of bounds read flaw has been discovered in libxml2. This flaw could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.


Affected upstream versions: 16
Fixed upstream versions: v2.14.0
Upstream repository: https://gitlab.gnome.org/GNOME/libxml2
Upstream fix commit: 5e7874015ef5ed8b2705eb2f7b0960f56f7760ea
CVE-2025-26625: git-lfs: Git LFS may write to arbitrary files via crafted symlinks
Component: git-lfs
Severity: Important
CWE: CWE-59 (Improper Link Resolution Before File Access ('Link Following'))
CVSS v3: 8.1 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N)
Public date: 2025-10-17T15:30:14.630000+00:00

A flaw was found in Git LFS. Running git lfs checkout and git lfs pull in a specially crafted repository, specifically with symbolic or hard links tracked by Git LFS and pointing to files outside the working tree or in a bare repository, can cause Git LFS to write to arbitrary file system locations accessible to the user running these commands.

Statement: This vulnerability can cause Git LFS to write to arbitrary file system locations accessible to the user running git lfs checkout and git lfs pull. These commands are typically run by regular users without special access to system files, limiting the impact of this issue.

Affected upstream versions: >= 0.5.2, < 3.7.1
Upstream repository: https://github.com/git-lfs/git-lfs
Upstream fix commit: 0cffe93176b870055c9dadbb3cc9a4a440e98396
CVE-2025-26791: dompurify: Mutation XSS in DOMPurify Due to Improper Template Literal Handling
Component: dompurify
Severity: Moderate
CWE: CWE-79 (Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'))
CVSS v3: 4.5 (CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N)
Public date: 2025-02-14T00:00:00+00:00

A flaw was found in DOMPurify. This vulnerability allows attackers to execute mutation-based Cross-site scripting (mXSS) via an incorrect template literal regular expression.


Affected upstream versions: <= 3.2.3
Fixed upstream versions: 3.2.4
Upstream repository: https://github.com/cure53/DOMPurify
Upstream fix commit: d18ffcb554e0001748865da03ac75dd7829f0f02
CVE-2025-27144: go-jose: Go JOSE's Parsing Vulnerable to Denial of Service
Component: go-jose
Severity: Moderate
CWE: CWE-770 (Allocation of Resources Without Limits or Throttling)
CVSS v3: 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)
Public date: 2025-02-24T22:22:22.863000+00:00

A flaw was found in GO-JOSE. In affected versions, when parsing compact JWS or JWE input, Go JOSE could use excessive memory. The code uses strings.Split(token, ".") to split JWT tokens, which is vulnerable to excessive memory consumption when processing maliciously crafted tokens with a large number of `.` characters. This issue could be exploied by sending numerous malformed tokens, leading to memory exhaustion and a Denial of Service.


Affected upstream versions: >= 4.0.0, < 4.0.5
Fixed upstream versions: v4.0.5
Upstream repository: https://github.com/go-jose/go-jose
Upstream fix commit: 99b346cec4e86d102284642c5dcbe9bb0cacfc22
CVE-2025-27151: redis: Redis Stack Buffer Overflow
Component: redis
Severity: Moderate
CWE: CWE-805 (Buffer Access with Incorrect Length Value)
CVSS v3: 2.5 (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L)
Public date: 2025-05-29T09:07:34.779000+00:00

A flaw was found in Redis. Using memcpy with the strlen filepath when copying a user-supplied file path into a fixed-size stack buffer in redis-check-aof results in a stack-based buffer overflow. This flaw allows a local attacker to trigger the overflow by providing a specially crafted file path, allowing potential code execution. The primary consequence is a possible denial of service.

Statement: The availability impact is limited to the instance of Redis and not to the system as a whole.

Affected upstream versions: >= 7.0.0, < 8.0.2
Fixed upstream versions: 8.0.2
Upstream repository: https://github.com/redis/redis
Upstream fix commit: 643b5db235cb82508e72f11c7b4bbfc7dc39be56
CVE-2025-27407: graphql-ruby: Remote code execution when loading a crafted GraphQL schema
Component: graphql-ruby
Severity: Important
CWE: CWE-94 (Improper Control of Generation of Code ('Code Injection'))
CVSS v3: 8.5 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H)
Public date: 2025-03-12T18:15:57.957000+00:00

A flaw was found in graphql-ruby. In affected versions of graphq-ruby, loading a malicious schema definition in the `GraphQL::Schema.from_introspection` or the `GraphQL::Schema::Loader.load` can cause remote code execution. Any system that loads a schema by JSON from an untrusted source is vulnerable, including those that use GraphQL::Client to load external schemas via GraphQL introspection.

Statement: This vulnerability is marked as Important rather than Critical because interaction with the vulnerable GraphQL library is restricted to only authenticated users in Red Hat Satellite. Satellite does not dynamically load schemas from external sources, further reducing the feasibility of exploitation.

Affected upstream versions: >= 1.11.5, < 1.11.8, >= 1.12.0, < 1.12.25, >= 1.13.0, < 1.13.24, >= 2.0.0, < 2.0.32, >= 2.1.0, < 2.1.14, >= 2.2.0, < 2.2.17, >= 2.3.0, < 2.3.21
Fixed upstream versions: v1.12.25
Upstream repository: https://github.com/rmosolgo/graphql-ruby
Upstream fix commit: 28233b16c0eb9d0fb7808f4980e061dc7507c4cd
CVE-2025-27516: jinja2: Jinja sandbox breakout through attr filter selecting format method
Component: jinja2
Severity: Important
CWE: CWE-1336 (Improper Neutralization of Special Elements Used in a Template Engine)
CVSS v3: 7.3 (CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H)
Public date: 2025-03-05T20:40:06.568000+00:00

A flaw was found in Jinja. In affected versions, an oversight in how the Jinja sandboxed environment interacts with the `|attr` filter allows an attacker who controls the content of a template to execute arbitrary Python code. To exploit the vulnerability, an attacker needs to control the content of a template. Whether that is the case depends on the type of application using Jinja. This vulnerability impacts users of applications that execute untrusted templates. Jinja's sandbox does catch calls to `str.format` and ensures they don't escape the sandbox. However, it's possible to use the `|attr` filter to get a reference to a string's plain format method, bypassing the sandbox.

Statement: This vulnerability is rated as important severity due to the potential for an attacker to bypass Jinja's sandbox by exploiting the |attr filter, by controlling template content, an attacker can execute arbitrary Python code, impacting the integrity, confidentiality, and availability of the system. While the attack requires user interaction to trigger untrusted templates, the risk is significant in applications that allow such templates to be executed.

Affected upstream versions: < 3.1.6
Fixed upstream versions: 3.1.6
Upstream repository: https://github.com/pallets/jinja
Upstream fix commit: 90457bbf33b8662926ae65cdde4c4c32e756e403
CVE-2025-27610: rack: rubygem-rack: Local File Inclusion in Rack::Static
Component: rack
Severity: Important
CWE: CWE-23 (Relative Path Traversal)
CVSS v3: 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N)
Public date: 2025-03-10T22:19:25.982000+00:00

A flaw was found in RackRubygems, where Rack::Static does not properly sanitize user-supplied paths before serving files. Specifically, encoded path traversal sequences are not correctly validated, allowing attackers to access files outside the designated static file directory. This flaw allows an attacker to gain access to all files under the specified root directory, provided they can determine the file's path.

Statement: This is an Important vulnerability because it allows attackers to bypass `urls:` restrictions and access unintended files under the `root:` directory using encoded path traversal. Since `Rack::Static` is often used to serve public assets, any sensitive files within the same root—like credentials, configs, or source code—can be exposed. The flaw breaks expected isolation between public and private files, and since it’s exploitable remotely without authentication, the impact is far more severe than a moderate issue.

PCS does not use Rack::StaticHandler to serve files; static files are served by Tornado.

Affected upstream versions: < 2.2.13, >= 3.0, < 3.0.14, >= 3.1, < 3.1.12
Fixed upstream versions: v3.2.0
Upstream repository: https://github.com/rack/rack
Upstream fix commit: 50caab74fa01ee8f5dbdee7bb2782126d20c6583
CVE-2025-27614: gitk: git script execution flaw
Component: gitk
Severity: Moderate
CVSS v3: 6.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L)
Public date: 2025-07-08T13:01:00+00:00

There's a vulnerability in gitk where an user can be tricked to run malicious scripts supplied by the attacker when running gitk filename command. When successfully exploited this vulnerability may result in arbitrary code execution.

Statement: The Red Hat Product Security team has rated this vulnerability as having a Moderate impact as it depends on the user to be tricked to run the command using the malicious file as parameter.

Affected upstream versions: >= 2.41.0, < 2.43.7, >= 2.44.0, < 2.44.4, >= 2.45.0, < 2.45.4, >= 2.46.0, < 2.46.4, >= 2.47.0, < 2.47.3, >= 2.48.0, < 2.48.2, >= 2.49.0, < 2.49.1, >= 2.50.0, < 2.50.1
Upstream repository: https://github.com/j6t/gitk
Upstream fix commit: 8e3070aa5e331be45d4d03e3be41f84494fce129
CVE-2025-27636: camel-http: org.apache.camel: bypass of header filters via specially crafted response
Component: camel-http
Severity: Moderate
CWE: CWE-644 (Improper Neutralization of HTTP Headers for Scripting Syntax)
CVSS v3: 6.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L)
Public date: 2025-03-10T00:00:00+00:00

A vulnerability was found in Apache Camel. This flaw allows an attacker to bypass filtering via a specially crafted request containing a certain combination of upper and lower case characters due to an issue in the default header filtering mechanism, which blocks headers starting with "Camel" or "camel."

Statement: This vulnerability is rated as having Moderate impact because it can only be triggered under certain configurations and does not enable complete takeover of the system. In order to be vulnerable, a system using the Apache Camel Framework must specifically be using the camel-bean component as a producer and the exchange is coming from a http-based consumer, such as HTTP component or platform-http. If exploitation occurs, an attacker could call other methods on that bean already in the classpath, but not from other arbitrary java beans, System.getenv, nor part of JDK itself.

Affected upstream versions: 4.10.0 < 4.10.2, 4.8.0 < 4.8.5, 3.10.0 < 3.22.4
Fixed upstream versions: 3.22.4, 4.10.2, 4.8.5
Upstream repository: https://github.com/apache/camel
Upstream fix commit: 781491b446921341f87a13824be4f7b5063776fc
CVE-2025-29774: xml-crypto: xml-crypto Vulnerable to XML Signature Verification Bypass via Multiple SignedInfo References
Component: xml-crypto
Severity: Important
CWE: CWE-347 (Improper Verification of Cryptographic Signature)
CVSS v3: 9.1 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N)
Public date: 2025-03-14T17:05:53.943000+00:00

A flaw was found in the xml-crypto library for Node.js. An attacker can exploit this vulnerability to bypass authentication or authorization mechanisms in systems that rely on xml-crypto to verify signed XML documents. The vulnerability allows an attacker to modify a valid signed XML message in a way that still passes signature verification checks.


Affected upstream versions: >= 4.0.0, < 6.0.1, >= 3.0.0, < 3.2.1, < 2.1.6
Fixed upstream versions: v3.2.1
Upstream repository: https://github.com/node-saml/xml-crypto
Upstream fix commit: 28f92218ecbb8dcbd238afa4efbbd50302aa9aed
CVE-2025-29775: xml-crypto: xml-crypto Vulnerable to XML Signature Verification Bypass via DigestValue Comment
Component: xml-crypto
Severity: Important
CWE: CWE-347 (Improper Verification of Cryptographic Signature)
CVSS v3: 9.1 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N)
Public date: 2025-03-14T17:11:05.590000+00:00

A flaw was found in the xml-crypto library for Node.js. An attacker can exploit this vulnerability to bypass authentication or authorization mechanisms in systems that rely on xml-crypto to verify signed XML documents. The vulnerability allows an attacker to modify a valid signed XML message in a way that still passes signature verification checks.


Affected upstream versions: >= 4.0.0, < 6.0.1, >= 3.0.0, < 3.2.1, < 2.1.6
Fixed upstream versions: v3.2.1
Upstream repository: https://github.com/node-saml/xml-crypto
Upstream fix commit: 28f92218ecbb8dcbd238afa4efbbd50302aa9aed
CVE-2025-29781: baremetal-operator/apis: Bare Metal Operator (BMO) can expose any secret from other namespaces via BMCEventSubscription CRD
Component: baremetal-operator/apis
Severity: Important
CWE: CWE-653 (Improper Isolation or Compartmentalization)
CVSS v3: 8.2 (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H)
Public date: 2025-03-17T21:37:31.856000+00:00

A flaw was found in the Bare Metal Operator (BMO) Kubernetes API component. BMO enables users to load Secrets from arbitrary namespaces upon deployment of the namespace-scoped Custom Resource `BMCEventSubscription`. In affected versions, an adversary using a Kubernetes account with only namespace level roles (e.g. a tenant controlling a namespace) may create a `BMCEventSubscription` in their authorized namespace and then load Secrets from their unauthorized namespaces to another authorized namespace via the Baremetal Operator, which can lead to the exposure of secrets and credential information.

Statement: This vulnerability is rated as Important for OpenShift Baremetal Operator, because RBAC is cluster-scoped and, while WATCH_NAMESPACE is set to openshift-machine-api by default, it is common for deployments to have a less restrictive value configured. It breaks Kubernetes' namespace isolation by allowing a user to create a BMCEventSubscription that references Secrets from unauthorized namespaces. In OpenShift, where Secrets often store high-value assets like kubeadmin credentials or cloud API keys, this enables unauthorized access to sensitive data across tenant boundaries. It effectively becomes a horizontal privilege escalation vector, allowing a namespace-scoped user to exfiltrate secrets intended for other components or tenants.  Given the minimal exploit complexity and high-impact potential, especially in multi-tenant environments, this issue is more severe than a moderate flaw and justifies a high CVSS rating.

Affected upstream versions: = 0.9.0, < 0.8.1
Fixed upstream versions: v0.10.0
Upstream repository: https://github.com/metal3-io/baremetal-operator
Upstream fix commit: 19f8443b1fe182f76dd81b43122e8dd102f8b94c
CVE-2025-29786: github.com/expr-lang/expr: Memory Exhaustion in Expr Parser with Unrestricted Input
Component: github.com/expr-lang/expr
Severity: Important
CWE: CWE-770 (Allocation of Resources Without Limits or Throttling)
CVSS v3: 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)
Public date: 2025-03-17T13:15:32.836000+00:00

A flaw was found in Expr. This vulnerability allows excessive memory usage and potential out-of-memory (OOM) crashes via unbounded input strings, where a malicious or inadvertent large expression can cause the parser to construct an extremely large Abstract Syntax Tree (AST), consuming excessive memory.


Affected upstream versions: < 1.17.0
Fixed upstream versions: v1.17.0
Upstream repository: https://github.com/expr-lang/expr
Upstream fix commit: 0d19441454426d2f58edb22c31f3ba5f99c7a26e
CVE-2025-30153: github.com/getkin/kin-openapi/openapi3filter: Improper Handling of Highly Compressed Data (Data Amplification) in github.com/getkin/kin-openapi/openapi3filter
Component: github.com/getkin/kin-openapi/openapi3filter
Severity: Important
CWE: CWE-409 (Improper Handling of Highly Compressed Data (Data Amplification))
CVSS v3: 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)
Public date: 2025-03-19T16:03:26.947000+00:00

A flaw was found in kin-openapi. This vulnerability allows excessive memory consumption via upload of a crafted ZIP file (a "ZIP bomb").


Affected upstream versions: < 0.131.0
Fixed upstream versions: v0.131.0
Upstream repository: https://github.com/getkin/kin-openapi
Upstream fix commit: 67f0b233ffc01332f7d993f79490fbea5f4455f1
CVE-2025-30204: golang-jwt/jwt: jwt-go allows excessive memory allocation during header parsing
Component: golang-jwt/jwt
Severity: Important
CWE: CWE-405 (Asymmetric Resource Consumption (Amplification))
CVSS v3: 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)
Public date: 2025-03-21T21:42:01.382000+00:00

A flaw was found in the golang-jwt implementation of JSON Web Tokens (JWT). In affected versions, a malicious request with specially crafted Authorization header data may trigger an excessive consumption of resources on the host system. This issue can cause significant performance degradation or an application crash, leading to a denial of service.


Affected upstream versions: >= 3.2.0, < 4.5.2, >= 5.0.0-rc.1, < 5.2.2
Fixed upstream versions: v5.2.2
Upstream repository: https://github.com/golang-jwt/jwt
Upstream fix commit: 0951d184286dece21f73c85673fd308786ffe9c3
CVE-2025-31115: xz: XZ has a heap-use-after-free bug in threaded .xz decoder
Component: xz
Severity: Important
CWE: CWE-823 (Use of Out-of-range Pointer Offset)
CVSS v3: 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)
Public date: 2025-04-03T16:57:05.488000+00:00

A flaw was found in the XZ Utils library. In affected versions, the multithreaded .xz decoder in liblzma has a bug where invalid input can trigger a heap use-after-free condition, allowing writes to an address based on the null pointer plus an offset. This issue may result in a crash or other undefined behavior. Applications and libraries that use the `lzma_stream_decoder_mt` function are affected.

Statement: This vulnerability is rated as important severity because a flaw exists in XZ Utils multithreaded .xz decoder within liblzma. When processing specially crafted compressed input, the decoder can trigger a heap use-after-free condition and perform memory writes to an address calculated from a null pointer plus an offset. These issues can reliably cause application crashes, leading to denial of service, and may allow memory corruption that affects process stability and security. Systems or applications decompressing untrusted .xz data with multithreaded decoding are at heightened risk of disruption and compromise.

Affected upstream versions: >= 5.3.3alpha, < 5.8.1
Fixed upstream versions: v5.8.1
Upstream repository: https://github.com/tukaani-project/xz
Upstream fix commit: d5a2ffe41bb77b918a8c96084885d4dbe4bf6480
CVE-2025-31133: runc: container escape via 'masked path' abuse due to mount race conditions
Component: runc
Severity: Important
CWE: CWE-59 (Improper Link Resolution Before File Access ('Link Following'))
CVSS v3: 8.2 (CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H)
Public date: 2025-11-05T00:00:00+00:00

A flaw was found in runc. This flaw exploits an issue with how masked paths are implementedin runc. When masking files, runc will bind-mount the container's /dev/null inode on top of the file. However, if an attacker can replace /dev/null with a symlink to some other procfs file, runc will instead bind-mount the symlink target read-write.

Statement: Red Hat considers this as an Important flaw since the impact is limited to local attack with minimal privileges in order to jeopardize the environment.

Affected upstream versions: < 1.2.8, >= 1.3.0-rc.1, < 1.3.3, >= 1.4.0-rc.1, <= 1.4.0-rc.3
Fixed upstream versions: v1.5.0
Upstream repository: https://github.com/opencontainers/runc
Upstream fix commit: 1a30a8f3d921acbbb6a4bb7e99da2c05f8d48522
CVE-2025-31492: mod_auth_openidc: mod_auth_openidc allows OIDCProviderAuthRequestMethod POSTs to leak protected data
Component: mod_auth_openidc
Severity: Important
CWE: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)
CVSS v3: 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N)
Public date: 2025-04-06T20:02:20.511000+00:00

A flaw was found in mod_auth_openidc, an OpenID Connect authentication module for Apache HTTP Server. This vulnerability allows unauthenticated users to access protected content via crafted HTTP POST requests to protected resources when no application-level gateway is present.

Statement: This vulnerability marked as important severity rather than moderate due to its direct breach of access control, one of the core pillars of web application security. The flaw allows unauthenticated users to access sensitive protected content simply by triggering a specific OpenID Connect flow, bypassing the intended authentication checks. This is not merely a misconfiguration or theoretical risk — it results from a flawed control path in mod_auth_openidc where the module returns OK for unauthenticated requests, and httpd proceeds to serve protected content. The vulnerability affects environments without strict external request validation (e.g., no reverse proxy or WAF), making it highly impactful in real-world deployments.

Affected upstream versions: < 2.4.16.11
Fixed upstream versions: v2.4.16.11
Upstream repository: https://github.com/OpenIDC/mod_auth_openidc
Upstream fix commit: b59b8ad63411857090ba1088e23fe414c690c127
CVE-2025-31498: c-ares: c-ares has a use-after-free in read_answers()
Component: c-ares
Severity: Moderate
CWE: CWE-416 (Use After Free)
CVSS v3: 7 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H)
Public date: 2025-04-08T13:53:11.232000+00:00

A flaw was found in c-ares. This vulnerability allows a remote or local attacker to cause a use-after-free, potentially leading to application-level denial of service or other unexpected behavior via manipulation of DNS responses or network conditions during query processing.

Statement: This vulnerability is rated as moderate severity rather than important because successful exploitation requires a complex and unlikely set of conditions. While it is a use-after-free bug—typically a serious issue—the ability to trigger it remotely is largely theoretical. An attacker would need to control an upstream DNS server and simultaneously flood the target with ICMP UNREACHABLE packets to influence network behavior precisely, a scenario that is difficult to achieve in practice. Additionally, local exploitation depends on manipulating low-level socket behavior to induce send() or write() failures, which also requires elevated system influence or specific environmental conditions.

Affected upstream versions: >= 1.32.3, < 1.34.5
Upstream repository: https://github.com/c-ares/c-ares
Upstream fix commit: 29d38719112639d8c0ba910254a3dd4f482ea2d1