CVE-2026-8711

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.9%, top 44% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

NGINX JavaScript has a vulnerability when the js_fetch_proxy directive is configured with at least one client-controlled NGINX variable (for example, $http_*, $arg_*, $cookie_*) and a location invoking the ngx.fetch() operation from NGINX JavaScript. An unauthenticated attacker can exploit this vulnerability by sending crafted HTTP requests. This may cause a heap buffer overflow in the NGINX worker process leading to a restart. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR.

Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
44(Track)
EG Risk 44/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
Severity98% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
56%
KEV
Not listed

Published

May 19, 2026

Last Modified

July 23, 2026

Advisory Details (1)

Auto-updated Jul 24, 2026
No patch confirmed yet.
generic

myF5

https://my.f5.com/manage/s/article/K000161307

Vendor Advisories for CVE-2026-8711(2)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntunjs (0.9.4-1ubuntu0.1~esm1) @ resolute2026-07-26ubuntu

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

(1)

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 12× in last 7d / 47× 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 157 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-8711?
CVE-2026-8711 is a critical vulnerability published on May 19, 2026. NGINX JavaScript has a vulnerability when the jsfetchproxy directive is configured with at least one client-controlled NGINX variable (for example, $http*, $arg, $cookie_) and a location invoking the ngx.fetch() operation from NGINX JavaScript. An unauthenticated attacker can exploit this…
When was CVE-2026-8711 disclosed?
CVE-2026-8711 was first published in the National Vulnerability Database on May 19, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-8711 actively exploited?
CVE-2026-8711 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 44.4% of all scored CVEs.
What is the CVSS score of CVE-2026-8711?
CVE-2026-8711 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-8711?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-8711, 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-2026-8711

Explore →

Is Your Infrastructure Affected by CVE-2026-8711?

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

Start Free Scan →Browse All CVEs