CVE-2026-85719

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (29th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-81904 (ENISA EUVD)Source: ENISA EUVD

7.5EG
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.4%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. From 2.1.0 until 2.16.1 and 3.0.12, requests using an authenticated SOCKS proxy can expose the proxy's credentials to the origin because NettyRequestFactory and NettyRequestSender attach Proxy-Authorization without confirming that the request is being sent to an HTTP proxy. With preemptive proxy authentication, the header is attached to a plaintext HTTP request, exposing credentials such as directly reversible Basic credentials to the origin. With the default non-preemptive flow, a hostile origin can return a 407 response and ProxyUnauthorized407Interceptor sends the proxy credentials through the existing SOCKS tunnel, including NTLM, Kerberos, and SPNEGO credentials. Releases before 2.1.0 lack SOCKS proxy support. This issue is fixed in versions 2.16.1 and 3.0.12.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 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.4%
EPSS %ILE
29th
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 (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). 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, and whom BOD 26-04 binds: 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.

The score's inputs: 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

September 17, 2026

Last Modified

September 24, 2026

Advisory Details (5)

Auto-updated Sep 17, 2026
Patch available. Sources: github, github_commit.
GitHub commit Patch Available

commit be439b2ec773 (AsyncHttpClient/async-http-client)

Patch available: AsyncHttpClient/async-http-client async-http-client-project-3.0.12 (contains commit be439b2ec773)

https://github.com/AsyncHttpClient/async-http-client/commit/be439b2ec773d12d61914c238d3e8eeaa6f0ba21
GitHub commit Patch Available

commit abaa8bd260be (AsyncHttpClient/async-http-client)

Patch available: AsyncHttpClient/async-http-client async-http-client-project-2.16.1 (contains commit abaa8bd260be)

https://github.com/AsyncHttpClient/async-http-client/commit/abaa8bd260beda3b85825ff95069ed11eaf4ca8d
GitHub commit Patch Available

commit 718ed2e86126 (AsyncHttpClient/async-http-client)

Patch available: AsyncHttpClient/async-http-client async-http-client-project-2.16.1 (contains commit 718ed2e86126)

https://github.com/AsyncHttpClient/async-http-client/commit/718ed2e86126663a88ea3db7a88cbbf93f0069b5
GitHub commit Patch Available

commit 4d887704dec2 (AsyncHttpClient/async-http-client)

Patch available: AsyncHttpClient/async-http-client async-http-client-project-3.0.12 (contains commit 4d887704dec2)

https://github.com/AsyncHttpClient/async-http-client/commit/4d887704dec22027310f66c81503226722e9bd23
GitHub advisoryMentions a patch (unverified)

SOCKS proxy credentials sent to the origin server over plaintext HTTP · Advisory · AsyncHttpClient/async-http-client · GitHub

Affected: 3.0.12 on the 3.x line and in 2.16.1 on the 2.x line. Proxy credentials are attac

https://github.com/AsyncHttpClient/async-http-client/security/advisories/GHSA-x5w6-vm3f-pp6f

Affected Packages

(1 across 1 ecosystem)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
async-http-client2.12.3-1, 2.12.3-1+deb12u1
  • every version on: no fix on record
—

Weakness Classification(2)

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

Data Freshness Timeline

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

  1. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  3. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  4. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  5. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  6. 2026-10-27 19:56 UTCEG score recompute
  7. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  8. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  9. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  10. 2026-10-25 13:55 UTCEG score recompute
  11. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  12. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  13. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  14. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  15. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  16. 2026-10-20 07:30 UTCEG score recompute
  17. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  18. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  19. 2026-10-18 03:05 UTCEG score recompute
  20. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  21. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  22. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  23. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  24. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  25. 2026-10-13 05:24 UTCEG score recompute
Show 55 more
  1. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  2. 2026-10-12 14:52 UTCEG score recompute
  3. 2026-10-11 19:17 UTCEG score recompute
  4. 2026-10-11 16:34 UTCEG score recompute
  5. 2026-10-11 13:51 UTCEG score recompute
  6. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  7. 2026-10-11 03:42 UTCEG score recompute
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  9. 2026-10-10 03:56 UTCEG score recompute
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  11. 2026-10-08 18:02 UTCEG score recompute
  12. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  13. 2026-10-08 05:23 UTCEG score recompute
  14. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  15. 2026-10-06 17:38 UTCEG score recompute
  16. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  17. 2026-10-05 19:08 UTCEG score recompute
  18. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  19. 2026-10-05 07:52 UTCEG score recompute
  20. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  21. 2026-10-03 22:07 UTCEG score recompute
  22. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  23. 2026-10-02 23:37 UTCEG score recompute
  24. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  25. 2026-10-02 00:09 UTCEG score recompute
  26. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  27. 2026-10-01 00:37 UTCEG score recompute
  28. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  29. 2026-09-30 01:59 UTCEG score recompute
  30. 2026-09-29 03:26 UTCEG score recompute
  31. 2026-09-28 16:11 UTCEG score recompute
  32. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  33. 2026-09-27 17:37 UTCEG score recompute
  34. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  35. 2026-09-26 19:04 UTCEG score recompute
  36. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  37. 2026-09-26 07:44 UTCEG score recompute
  38. 2026-09-24 18:03 UTCEG score recompute
  39. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  40. 2026-09-23 19:15 UTCEG score recompute
  41. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  42. 2026-09-22 20:45 UTCEG score recompute
  43. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  44. 2026-09-21 22:14 UTCEG score recompute
  45. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  46. 2026-09-20 23:44 UTCEG score recompute
  47. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  48. 2026-09-20 01:13 UTCEG score recompute
  49. 2026-09-19 02:41 UTCEG score recompute
  50. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  51. 2026-09-18 15:26 UTCEG score recompute
  52. 2026-09-18 14:54 UTCEG score recompute
  53. 2026-09-17 17:56 UTCEG score recompute
  54. 2026-09-17 15:54 UTCEG score recomputeFirst assessed: 7.5 HIGH
  55. 2026-09-17 15:54 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-85719?
CVE-2026-85719 is a high-severity vulnerability; its CVE record was published on September 17, 2026. The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. From 2.1.0 until 2.16.1 and 3.0.12, requests using an authenticated SOCKS proxy can expose the proxy's credentials to the origin because NettyRequestFactory and…
When was the CVE record for CVE-2026-85719 published?
The CVE record for CVE-2026-85719 was published on September 17, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-85719 actively exploited?
CVE-2026-85719 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (29th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-85719?
CVE-2026-85719 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-85719?
A fix for CVE-2026-85719 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-85719?

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