PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-5435 The GNU C Library CVE debrief

The GNU C Library versions 2.2 and newer contain a vulnerability due to the deprecated functions ns_printrrf, ns_printrr, and fp_nquery failing to enforce the caller-supplied buffer length. This can result in an out-of-bounds write when printing TSIG records. The vulnerability has a CVSS score of 7.3 and is classified as HIGH. Affected product deployments should be identified, and owners assigned for follow-up. Official advisories and CVE records should be reviewed to validate affected scope, severity, and vendor guidance.

Vendor
The GNU C Library
Product
glibc
CVSS
HIGH 7.3
CISA KEV
Not listed in stored evidence
Original CVE published
2026-04-28
Original CVE updated
2026-07-14
Advisory published
2026-04-28
Advisory updated
2026-07-14

Who should care

Users of GNU C Library version 2.2 and newer should be aware of this vulnerability and take steps to mitigate it. Affected operators, platforms, vulnerability-management, and security teams should review the vulnerability and implement necessary controls. Compensating controls should be reviewed for exposed systems while remediation is scheduled and verified.

Technical summary

The GNU C Library versions 2.2 and newer contain a vulnerability due to the deprecated functions ns_printrrf, ns_printrr, and fp_nquery failing to enforce the caller-supplied buffer length. This can result in an out-of-bounds write when printing TSIG records. The vulnerability has a CVSS score of 7.3 and is classified as HIGH. Affected product context and defensive impact should be considered when assessing this vulnerability. Source-grounded technical framing is necessary to understand the vulnerability without unsupported root-cause or exploit claims.

Defensive priority

High priority should be given to patching or mitigating this vulnerability, as it can lead to potential code execution.

Recommended defensive actions

  • Apply patches or updates provided by the vendor
  • Use compensating controls to limit the impact of the vulnerability
  • Monitor systems for potential exploitation
  • Review relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed

Evidence notes

The vulnerability is documented in the NVD and CVE records. The GNU C Library project has acknowledged the issue and provided patches. Evidence limits suggest that further verification is required to confirm affected scope and severity. Defenders should verify system configurations, review compensating controls, and monitor for potential exploitation. Additional review of vendor guidance and mitigation strategies is recommended.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-5435 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-5435

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-5435 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-5435

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Mitigation or vendor reference

    Unverified legacy reference

    URL: https://inbox.sourceware.org/libc-announce/[email protected]/T/

    3ff69d7a-14f2-4f67-a097-88dee7810d18 - Third Party Advisory

  • Source reference

    Unverified legacy reference

    URL: https://cert-portal.siemens.com/productcert/html/ssa-082556.html

    0b142b55-0307-4c5a-b3c9-f314f3fb7c5e

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.