CVE-2026-54478

LOWPre-NVD 3.73.7
EchelonGraph scoreMEDIUM confidence

Score 3.7 from GitHub Security Advisory (severity: LOW) published 2026-07-22. a secondary CVSS source baseline 3.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
3.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.7Exploit: None knownExposed: 0

A fix is available — apply it.

In NLnet Labs Unbound 1.18.0 up to and including 1.25.1, when Unbound listens on a 'proxy-protocol-port' interface with 'answer-cookie: yes', the RFC 9018 server-cookie SipHash is computed over the proxy's wire address instead of the PROXYv2-declared client. One server cookie obtained through a given proxy node therefore validates for every PROXYv2-declared source behind that node. On a UDP+proxy-protocol front, an off-path attacker can harvest one cookie with a single legitimate query, then replay it under any spoofed source and pass DNS Cookie checks that were deployed to defeat this in the first place.

CVSS v3
3.7
EG Score
3.7(medium)
EG Risk
17(Track)
EG Risk 17/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity37% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

July 22, 2026

Last Modified

July 24, 2026

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatunbound-main-1.25.2-0.1.hum12026-07-22redhat

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

(5 across 5 ecosystems)
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
unbound1.25.2-r0
Debian:11(1)
PackageVulnerable rangeFixed inDependents
unbound1.13.1-1 ... 1.25.2-1 (47 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
unbound1.17.1-2 ... 1.26.0-2 (25 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
unbound1.22.0-2 ... 1.26.0-2 (15 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
unbound1.22.0-2 ... 1.25.1-1 (9 versions)1.25.2-1

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 53× 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.

Showing the most recent 100 of 110 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-54478?
CVE-2026-54478 is a low vulnerability published on July 22, 2026. In NLnet Labs Unbound 1.18.0 up to and including 1.25.1, when Unbound listens on a 'proxy-protocol-port' interface with 'answer-cookie: yes', the RFC 9018 server-cookie SipHash is computed over the proxy's wire address instead of the PROXYv2-declared client. One server cookie obtained through a…
When was CVE-2026-54478 disclosed?
CVE-2026-54478 was first published in the National Vulnerability Database on July 22, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54478 actively exploited?
CVE-2026-54478 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 92.5% of all scored CVEs.
What is the CVSS score of CVE-2026-54478?
CVE-2026-54478 has a CVSS v3 base score of 3.7 (NVD).
How do I remediate CVE-2026-54478?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54478, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54478

Explore →

Is Your Infrastructure Affected by CVE-2026-54478?

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