CVE-2026-19538

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-01. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Fixed versions, as the CVE record's CNA (NLnet Labs) states them: "This issue is fixed in 4.15.1 and all later versions."

The BLOCKED access control list items that are evaluated to deny access on the the proxy protocol port can be bypassed completely when connecting over TCP or TLS and sending the query twice on connection that is kept open.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/100

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 (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.2%
EPSS %ILE
13th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (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

August 26, 2026

Last Modified

September 8, 2026

Advisory Details (1)

Auto-updated Aug 26, 2026
Patch available.

Vendor Advisories for CVE-2026-19538(1)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
nsd4.10.1-1 ... 4.9.1-1 (25 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
nsd4.12.0-1 ... 4.15.2-1 (16 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
nsd4.12.0-1 ... 4.15.0~rc1-1 (14 versions)
  • every version up to 4.15.1-1: fixed in 4.15.1-1
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 99× 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 100 of 167 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. None are among the latest 100 rows. The 67 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-19538?
CVE-2026-19538 is a high-severity vulnerability; its CVE record was published on August 26, 2026. The BLOCKED access control list items that are evaluated to deny access on the the proxy protocol port can be bypassed completely when connecting over TCP or TLS and sending the query twice on connection that is kept open.
When was CVE-2026-19538 made public?
CVE-2026-19538 was made public on August 26, 2026: that is the date its CVE record's CNA, NLnet Labs, gives for when the vulnerability was made public. The CVE record itself was published on August 26, 2026. EchelonGraph's copy of the record carries a last-modified date of September 8, 2026; the record at its source may have been updated since.
Is CVE-2026-19538 actively exploited?
CVE-2026-19538 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (13th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-19538?
CVE-2026-19538 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-19538?
A fix for CVE-2026-19538 is available: update to the fixed version the vendor names in its advisory. Fixed versions, as the CVE record's CNA (NLnet Labs) states them: "This issue is fixed in 4.15.1 and all later versions." The vendor advisories EchelonGraph has for CVE-2026-19538 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-2026-19538

Explore →

Is Your Infrastructure Affected by CVE-2026-19538?

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