CVE-2025-40778

HIGHNVD 8.68.6—
EchelonGraph scoreMEDIUM confidence

Score 8.6 from GitHub Security Advisory (severity: HIGH) published 2025-10-22. NVD baseline CVSS 8.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
8.6
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 8.6Exploit: NoneExposed: 0

A fix is available — apply it.

Under certain circumstances, BIND is too lenient when accepting records from answers, allowing an attacker to inject forged data into the cache. This issue affects BIND 9 versions 9.11.0 through 9.16.50, 9.18.0 through 9.18.39, 9.20.0 through 9.20.13, 9.21.0 through 9.21.12, 9.11.3-S1 through 9.16.50-S1, 9.18.11-S1 through 9.18.39-S1, and 9.20.9-S1 through 9.20.13-S1.

CVSS v3
8.6
EG Score
8.6(medium)
EPSS
40.0%
KEV
Not listed

Published

October 22, 2025

Last Modified

April 15, 2026

References (3)

Vendor Advisories for CVE-2025-40778(20)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(30)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatbind-main-9.18.48-1.hum12026-04-07redhat
redhatrhcos-415.92.202601271320-02026-02-05redhat
redhatrhcos-414.92.202601191325-02026-01-30redhat
redhatopenshift-serverless-1/logic-swf-devmode-rhel8:1.36.0-72026-01-22redhat
redhatrhcos-4.19.9.6.202601130152-02026-01-22redhat
redhatrhcos-413.92.202601130113-02026-01-22redhat
redhatrhcos-417.94.202601120213-02026-01-22redhat
redhatrhcos-412.86.202601061735-02026-01-15redhat
redhatrhcos-416.94.202601071926-02026-01-15redhat
redhatrhcos-418.94.202601071817-02026-01-15redhat
redhatrhcos-4.20.9.6.202601052146-02026-01-14redhat
redhatbind-32:9.8.2-0.68.rc1.el6_10.172025-12-17redhat
redhatbind-32:9.11.4-26.P2.el7_9.192025-11-26redhat
redhatbind9.16-32:9.16.23-0.7.el8_6.92025-11-26redhat
redhatbind9.16-32:9.16.23-0.14.el8_8.72025-11-24redhat
redhatdiscovery/discovery-ui-rhel9:2.4.0-17636561522025-11-24redhat
redhatbind-32:9.16.23-11.el9_2.92025-11-20redhat
redhatbind-32:9.16.23-18.el9_4.102025-11-20redhat
redhatbind-32:9.16.23-1.el9_0.112025-11-20redhat
redhatbind-32:9.11.26-4.el8_4.82025-11-19redhat
redhatbind-32:9.11.36-3.el8_6.112025-11-19redhat
redhatbind-32:9.11.36-8.el8_8.82025-11-19redhat
redhatbind-32:9.11.13-6.el8_2.112025-11-19redhat
redhatbind9.18-32:9.18.29-5.el9_7.22025-11-12redhat
redhatbind-32:9.16.23-34.el9_7.12025-11-12redhat
redhatbind-32:9.18.33-10.el10_1.22025-11-11redhat
redhatbind9.18-32:9.18.29-4.el9_6.22025-11-10redhat
redhatbind-32:9.16.23-31.el9_6.22025-11-10redhat
redhatbind-32:9.18.33-4.el10_0.22025-11-06redhat
redhatbind-32:9.11.36-16.el8_10.62025-11-06redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(12)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 13× in last 7d / 50× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-16 17:02 UTCEPSS rescore
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 16:57 UTCEPSS rescore
  4. 2026-07-15 01:59 UTCEPSS rescore
  5. 2026-07-15 01:59 UTCEPSS rescore
  6. 2026-07-13 22:29 UTCEPSS rescore
  7. 2026-07-13 22:29 UTCEPSS rescore
  8. 2026-07-13 06:12 UTCEPSS rescore
  9. 2026-07-12 05:46 UTCEPSS rescore
  10. 2026-07-11 08:27 UTCEPSS rescore
  11. 2026-07-11 08:27 UTCEPSS rescore
  12. 2026-07-09 19:09 UTCEPSS rescore
  13. 2026-07-09 19:09 UTCEPSS rescore
  14. 2026-07-07 13:45 UTCEPSS rescore
  15. 2026-07-06 16:27 UTCEPSS rescore
  16. 2026-07-06 16:27 UTCEPSS rescore
  17. 2026-07-06 02:23 UTCEPSS rescore
  18. 2026-07-05 02:30 UTCEPSS rescore
  19. 2026-07-04 06:30 UTCEPSS rescore
  20. 2026-07-01 15:06 UTCEPSS rescore
  21. 2026-07-01 15:06 UTCEPSS rescore
  22. 2026-06-30 23:22 UTCEPSS rescore
  23. 2026-06-30 23:22 UTCEPSS rescore
  24. 2026-06-29 14:06 UTCEPSS rescore
  25. 2026-06-29 14:06 UTCEPSS rescore
Show 63 more
  1. 2026-06-28 14:07 UTCEPSS rescore
  2. 2026-06-28 14:07 UTCEPSS rescore
  3. 2026-06-28 04:55 UTCEPSS rescore
  4. 2026-06-28 04:55 UTCEPSS rescore
  5. 2026-06-27 03:08 UTCEPSS rescore
  6. 2026-06-27 03:08 UTCEPSS rescore
  7. 2026-06-25 13:49 UTCEPSS rescore
  8. 2026-06-25 13:49 UTCEPSS rescore
  9. 2026-06-24 14:04 UTCEPSS rescore
  10. 2026-06-24 14:04 UTCEPSS rescore
  11. 2026-06-23 21:32 UTCEPSS rescore
  12. 2026-06-23 21:32 UTCEPSS rescore
  13. 2026-06-22 14:25 UTCEPSS rescore
  14. 2026-06-22 14:25 UTCEPSS rescore
  15. 2026-06-21 14:56 UTCEPSS rescore
  16. 2026-06-21 14:56 UTCEPSS rescore
  17. 2026-06-21 01:59 UTCEPSS rescore
  18. 2026-06-21 01:59 UTCEPSS rescore
  19. 2026-06-19 19:25 UTCEPSS rescore
  20. 2026-06-19 19:25 UTCEPSS rescore
  21. 2026-06-18 17:52 UTCEPSS rescore
  22. 2026-06-18 17:52 UTCEPSS rescore
  23. 2026-06-17 17:52 UTCEPSS rescore
  24. 2026-06-16 17:52 UTCEPSS rescore
  25. 2026-06-16 17:52 UTCEPSS rescore
  26. 2026-06-14 23:17 UTCEPSS rescore
  27. 2026-06-12 23:11 UTCEPSS rescore
  28. 2026-06-11 14:00 UTCEPSS rescore
  29. 2026-06-10 22:18 UTCEPSS rescore
  30. 2026-06-08 14:16 UTCEPSS rescore
  31. 2026-06-08 14:16 UTCEPSS rescore
  32. 2026-06-07 15:24 UTCEPSS rescore
  33. 2026-06-06 13:47 UTCEPSS rescore
  34. 2026-06-06 13:47 UTCEPSS rescore
  35. 2026-06-05 22:46 UTCEPSS rescore
  36. 2026-06-05 22:46 UTCEPSS rescore
  37. 2026-06-02 20:12 UTCEPSS rescore
  38. 2026-06-01 13:51 UTCEPSS rescore
  39. 2026-06-01 13:51 UTCEPSS rescore
  40. 2026-05-31 22:30 UTCEPSS rescore
  41. 2026-05-31 22:30 UTCEPSS rescore
  42. 2026-05-31 00:16 UTCEPSS rescore
  43. 2026-05-29 13:44 UTCEPSS rescore
  44. 2026-05-28 13:44 UTCEPSS rescore
  45. 2026-05-28 13:44 UTCEPSS rescore
  46. 2026-05-28 13:44 UTCEPSS rescore
  47. 2026-05-28 13:44 UTCEPSS rescore
  48. 2026-05-27 13:40 UTCEPSS rescore
  49. 2026-05-27 13:40 UTCEPSS rescore
  50. 2026-05-27 13:40 UTCEPSS rescore
  51. 2026-05-27 13:40 UTCEPSS rescore
  52. 2026-05-22 21:16 UTCEPSS rescore
  53. 2026-05-22 21:16 UTCEPSS rescore
  54. 2026-05-22 21:16 UTCEPSS rescore
  55. 2026-05-22 21:16 UTCEPSS rescore
  56. 2026-05-21 06:00 UTCEG score recompute
  57. 2026-05-21 06:00 UTCVendor advisory
  58. 2026-05-21 05:59 UTCGHSA enrichment
  59. 2026-05-20 11:21 UTCEPSS rescore
  60. 2026-05-20 11:21 UTCEPSS rescore
  61. 2026-05-20 11:21 UTCEPSS rescore
  62. 2026-05-20 11:21 UTCEPSS rescore
  63. 2026-05-18 21:31 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-40778?
CVE-2025-40778 is a high vulnerability published on October 22, 2025. Under certain circumstances, BIND is too lenient when accepting records from answers, allowing an attacker to inject forged data into the cache. This issue affects BIND 9 versions 9.11.0 through 9.16.50, 9.18.0 through 9.18.39, 9.20.0 through 9.20.13, 9.21.0 through 9.21.12, 9.11.3-S1 through…
When was CVE-2025-40778 disclosed?
CVE-2025-40778 was first published in the National Vulnerability Database on October 22, 2025, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-40778 actively exploited?
CVE-2025-40778 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 40.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-40778?
CVE-2025-40778 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2025-40778?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-40778, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-40778

Explore →

Is Your Infrastructure Affected by CVE-2025-40778?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs