CVE-2026-42533

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — Patch released this weekElevated
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 4%CVSS: 8.1Exploit: Elevated riskExposed: 0

A fix is available — apply it.

A vulnerability exists in NGINX Plus and NGINX Open Source when a map directive uses regex matching and a string expression references the map's regex capture variables before referencing the map output variable. Alternatively, the same result could be achieved by using a non-cacheable variable in a string expression under certain conditions. An unauthenticated attacker along with conditions beyond their control 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.

Impact: This vulnerability may allow remote attackers to cause a denial-of-service (DoS) on the NGINX system or to possibly trigger a code execution. There is no control plane exposure; this is a data plane issue only.

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

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
52(Track*)
EG Risk 52/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
Severity81% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
4%
EPSS %ILE
91%
KEV
Not listed

Published

July 15, 2026

Last Modified

August 10, 2026

Advisory Details (1)

Auto-updated Jul 15, 2026
No patch confirmed yet.

Patch Availability(9)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntunginx-light (1.28.3-2ubuntu1.7) @ resolute2026-09-18ubuntu
ubuntunginx-light (1.28.3-2ubuntu1.11) @ resolute2026-09-18ubuntu
ubuntunginx-light (1.28.3-2ubuntu1.9) @ resolute2026-09-18ubuntu
redhatnginx:1.24-9080020260908110425.92026-09-14redhat
redhatnginx-2:1.26.3-6.el10_2.72026-09-14redhat
redhatnginx:1.24-8100020260908154808.489197e62026-09-14redhat
redhatnginx:1.26-9080020260908105507.92026-09-14redhat
redhatnginx-2:1.20.1-28.el9_8.62026-09-11redhat
redhatnginx-main-1.30.4-2.hum12026-07-26redhat

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

(8 across 8 ecosystems)
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
nginx1.26.3-r2
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
nginx1.28.3-r6
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
nginx1.28.3-r6
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
nginx1.30.4-r0
Debian:11(1)
PackageVulnerable rangeFixed inDependents
nginx1.18.0-6.1 ... 1.30.4-3 (80 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
nginx1.22.1-9 ... 1.30.4-5 (52 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
nginx1.26.3-3 ... 1.30.4-5 (39 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
nginx1.26.3-3 ... 1.30.4-2 (29 versions)1.30.4-3

Weakness Classification(1)

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

Additional Vendor Advisories

(8)

Data Freshness Timeline

(refreshed 17× in last 7d / 91× 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 261 total refreshes for this CVE.

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

Publicly available exploits

(2 references)

Working exploit code is in the public domain (2 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCimbas007/CVE-2026-42533
    First seen Jul 27, 2026

    nginx heap buffer overflow PoC — CVE-2026-42533 pre-auth RCE via two-pass capture clobbering. Crash confirmed on Ubuntu 24.04.

    Open source ↗
  • GitHub PoC0xCyberstan/CVE-2026-42533-Config-Scanner
    First seen Jul 4, 2026

    Static config scanner that flags nginx configs vulnerable to the complex_value two-pass capture-clobbering bug (regex map + regex capture → heap overflow / info leak).

    Open source ↗

Frequently asked(5)

What is CVE-2026-42533?
CVE-2026-42533 is a high vulnerability published on July 15, 2026. A vulnerability exists in NGINX Plus and NGINX Open Source when a map directive uses regex matching and a string expression references the map's regex capture variables before referencing the map output variable. Alternatively, the same result could be achieved by using a non-cacheable variable in…
When was CVE-2026-42533 disclosed?
CVE-2026-42533 was first published in the National Vulnerability Database on July 15, 2026, with the most recent update on August 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42533 actively exploited?
CVE-2026-42533 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4% probability of exploitation in the next 30 days, which ranks it in the top 9.0% of all scored CVEs.
What is the CVSS score of CVE-2026-42533?
CVE-2026-42533 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-42533?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42533, 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-42533

Explore →

Is Your Infrastructure Affected by CVE-2026-42533?

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