Cyber Resilience

CVE-2025-40775

Published
21 May 2025
Modified
17 June 2026
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.12 96th percentile
Risk Priority 67 floored blend · peak EPSS

Summary

CVE-2025-40775 is a high-severity Improper Handling of Undefined Values (CWE-232) vulnerability. Its CVSS base score is 7.5 (High).

Operationally, ranked in the top 4% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

When an incoming DNS protocol message includes a Transaction Signature (TSIG), BIND always checks it. If the TSIG contains an invalid value in the algorithm field, BIND immediately aborts with an assertion failure. This issue affects BIND 9 versions 9.20.0…

more

through 9.20.8 and 9.21.0 through 9.21.7.

CWE(s)

Related Threats

CVEs Like This One

CVE-2023-2968Shared CWE-232
CVE-2023-36848Shared CWE-232
CVE-2025-20314Shared CWE-232
CVE-2025-20192Shared CWE-232
CVE-2023-39914Shared CWE-232
CVE-2023-39915Shared CWE-232
CVE-2026-21689Shared CWE-232

Affected Assets

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Input validation directly rejects or sanitizes undefined/unsupported parameter values before they reach processing logic.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require proper input validation and error handling for undefined values.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development can detect missing handling of undefined values before release.

prevents

Secure development life cycle requires handling of invalid/undefined inputs during design and coding.

prevents

Application security requirements include validation of all parameters and handling of unsupported values.

prevents

Secure architecture principles mandate explicit handling of undefined or unsupported states.

prevents

Secure coding standards directly require defensive checks for undefined or unsupported parameter values.

References