CVE-2025-40780

HIGHNVD 8.68.6
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

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, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week
8.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.6Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In specific circumstances, due to a weakness in the Pseudo Random Number Generator (PRNG) that is used, it is possible for an attacker to predict the source port and query ID that BIND will use. This issue affects BIND 9 versions 9.16.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.16.8-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.6HIGHmedium confidence
EG Risk
54
EG Risk 54/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity86% × 45%
Impact severity (EG Severity): CVSS 8.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
38th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.6): severity, escalated by confirmed exploitation. This CVE's 8.6 is its impact severity (EG Severity), not escalated.

EG Severity
8.6 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 22, 2025

Last Modified

October 8, 2026

Advisory Details (2)

Auto-updated Sep 1, 2026
Patch available.
Web page

oss-security - ISC has disclosed three vulnerabilities in BIND 9 (CVE-2025-8677, CVE-2025-40778, CVE-2025-40780)

http://www.openwall.com/lists/oss-security/2025/10/22/1
Web page

CVE-2025-40780: Cache poisoning due to weak PRNG

https://kb.isc.org/docs/cve-2025-40780

Patch Availability(25)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntubind9-utils (1:9.20.11-1ubuntu2.1) @ questing2026-10-18ubuntu
ubuntudnsutils (1:9.18.30-0ubuntu0.20.04.2+esm1) @ focal2026-10-18ubuntu
redhatbind-main-9.18.48-1.hum12026-04-07redhat
redhatrhcos-415.92.202601271320-02026-02-05redhat
redhatrhcos-414.92.202601191325-02026-01-30redhat
redhatrhcos-4.19.9.6.202601130152-02026-01-22redhat
redhatrhcos-413.92.202601130113-02026-01-22redhat
redhatrhcos-417.94.202601120213-02026-01-22redhat
redhatrhcos-416.94.202601071926-02026-01-15redhat
redhatrhcos-412.86.202601061735-02026-01-15redhat
redhatrhcos-418.94.202601071817-02026-01-15redhat
redhatrhcos-4.20.9.6.202601052146-02026-01-14redhat
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-18.el9_4.102025-11-20redhat
redhatbind-32:9.16.23-1.el9_0.112025-11-20redhat
redhatbind-32:9.16.23-11.el9_2.92025-11-20redhat
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
redhatbind9.16-32:9.16.23-0.22.el8_10.42025-11-05redhat

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.

Affected Packages

(10 across 10 ecosystems)
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • every version up to 9.18.41-r0: fixed in 9.18.41-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • every version up to 9.18.41-r0: fixed in 9.18.41-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • every version up to 9.18.41-r0: fixed in 9.18.41-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • every version up to 9.20.15-r0: fixed in 9.20.15-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • every version up to 9.20.15-r0: fixed in 9.20.15-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • every version up to 9.20.15-r0: fixed in 9.20.15-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
bind91:9.16.15-1 ... 1:9.16.50-1~deb11u3 (15 versions)
  • every version up to 1:9.16.50-1~deb11u4: fixed in 1:9.16.50-1~deb11u4
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
bind91:9.18.12-1 ... 1:9.18.33-1~deb12u2 (12 versions)
  • every version up to 1:9.18.41-1~deb12u1: fixed in 1:9.18.41-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
bind91:9.20.11-4, 1:9.20.15-1~deb13u1~bpo12+1
  • every version up to 1:9.20.15-1~deb13u1: fixed in 1:9.20.15-1~deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
bind91:9.20.11-4, 1:9.20.15-1~deb13u1, 1:9.20.15-1~deb13u1~bpo12+1
  • every version up to 1:9.20.15-1: fixed in 1:9.20.15-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 10× in last 7d / 35× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 92 of 197 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 8 repeat rows among the latest 100 are merged into the row they repeat. The 105 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2025-40780?
CVE-2025-40780 is a high-severity vulnerability; its CVE record was published on October 22, 2025. In specific circumstances, due to a weakness in the Pseudo Random Number Generator (PRNG) that is used, it is possible for an attacker to predict the source port and query ID that BIND will use. This issue affects BIND 9 versions 9.16.0 through 9.16.50, 9.18.0 through 9.18.39, 9.20.0 through…
When was CVE-2025-40780 made public?
CVE-2025-40780 was made public on October 22, 2025: that is the date its CVE record's CNA, Internet Systems Consortium (ISC), gives for when the vulnerability was made public. The CVE record itself was published on October 22, 2025. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
Is CVE-2025-40780 actively exploited?
CVE-2025-40780 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (38th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-40780?
CVE-2025-40780 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2025-40780?
A fix for CVE-2025-40780 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-40780 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-40780

Explore →

Is Your Infrastructure Affected by CVE-2025-40780?

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