CVE-2026-42946

HIGHNVD 7.47.4
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.4 under NVD CVSS v3. EPSS exploit probability: 0.9% (59th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 6.5 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-05-13) is not newer than that change (2026-06-18), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
7.4EG
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.9%CVSS: 7.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A vulnerability exists in the ngx_http_scgi_module and ngx_http_uwsgi_module modules that may result in excessive memory allocation or an over-read of data. When scgi_pass or uwsgi_pass is configured, an unauthenticated attacker with man-in-the-middle (MITM) ability to control responses from an upstream server may be able to read the memory of the NGINX worker process or restart it.  Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

CVSS v3
7.4
EG Score
7.4HIGHmedium 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)
Severity74% × 45%
The EG Score, 7.4 of 10.
Exploitation0.9% × 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.9%
EPSS %ILE
59th
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

May 13, 2026

Last Modified

June 18, 2026

Advisory Details (1)

Auto-updated Jun 14, 2026
Patch available.

Vendor Advisories for CVE-2026-42946(1)

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

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntunginx-light (1.28.3-2ubuntu1.2) @ resolute2026-08-23ubuntu
ubuntunginx-light (1.10.3-0ubuntu0.16.04.5+esm7) @ xenial2026-08-23ubuntu

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 rangeFix by version rangeDependents
nginx—
  • every version up to 1.26.3-r1: fixed in 1.26.3-r1
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
nginx—
  • every version up to 1.28.3-r1: fixed in 1.28.3-r1
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
nginx—
  • every version up to 1.28.3-r1: fixed in 1.28.3-r1
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
nginx—
  • every version up to 1.30.1-r0: fixed in 1.30.1-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
nginx1.18.0-6.1 ... 1.18.0-6.1+deb11u5 (6 versions)
  • every version up to 1.18.0-6.1+deb11u6: fixed in 1.18.0-6.1+deb11u6
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
nginx1.22.1-9 ... 1.22.1-9+deb12u7 (8 versions)
  • every version up to 1.22.1-9+deb12u8: fixed in 1.22.1-9+deb12u8
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
nginx1.26.3-3 ... 1.26.3-3+deb13u5 (6 versions)
  • every version up to 1.26.3-3+deb13u6: fixed in 1.26.3-3+deb13u6
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
nginx1.26.3-3 ... 1.30.0-3 (19 versions)
  • every version up to 1.30.0-4: fixed in 1.30.0-4
—

Weakness Classification(2)

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

Additional Vendor Advisories

(2)

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 11× in last 7d / 26× 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 265 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 165 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-42946?
CVE-2026-42946 is a high-severity vulnerability; its CVE record was published on May 13, 2026. A vulnerability exists in the ngxhttpscgimodule and ngxhttpuwsgimodule modules that may result in excessive memory allocation or an over-read of data. When scgipass or uwsgipass is configured, an unauthenticated attacker with man-in-the-middle (MITM) ability to control responses from an upstream…
When was CVE-2026-42946 made public?
CVE-2026-42946 was made public on May 13, 2026: that is the date its CVE record's CNA, F5, Inc., gives for when the vulnerability was made public. The CVE record itself was published on May 13, 2026. EchelonGraph's copy of the record carries a last-modified date of June 18, 2026; the record at its source may have been updated since.
Is CVE-2026-42946 actively exploited?
CVE-2026-42946 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (59th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-42946?
CVE-2026-42946 has a CVSS v3 base score of 7.4 (NVD).
How do I remediate CVE-2026-42946?
A fix for CVE-2026-42946 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-42946 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-42946

Explore →

Is Your Infrastructure Affected by CVE-2026-42946?

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