Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-125283NGINX try_files vulnerability

Description

When NGINX Plus or NGINX Open Source is configured to use the try_files and alias directives with a map variable, certain combinations of regular expression captures in map and try_files can cause a segmentation fault in an NGINX worker process. Impact: An attacker could leverage this vulnerability to cause an NGINX worker process to terminate unexpectedly. 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.

Timeline

  1. ID reserved

    By f5

  2. · 9 days later

    Published

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-125283, by who scored it
Scored byCVSSScoreVector
f5CNA (assigner)4.0Medium6.9CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
f5CNA (assigner)3.1Medium5.3CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
NVDNVD · Received4.0Medium6.9CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS (exploitation in 30 days)
Not scored
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: partial

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 6.9.

Affected products

  • F5 · NGINX Plus

    • affected 37.1.0 – < 37.3.0.1
    • affected 37.0.0 – < 37.0.8.1
    • affected R33 – < *
  • F5 · NGINX Open Source

    • affected 1.31.0 – < 1.31.9
    • affected 1.30.0 – < 1.30.7
    • affected 0.9.6 – < *

What to do

Workaround: Avoid unnamed regex captures; use named captures instead. Do not reuse the same capture variable in other regex matches or for other purposes.

References

References1

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-125283 badge
[![CVE-2026-125283](https://cveledger.app/badge/CVE-2026-125283.svg)](https://cveledger.app/cve/CVE-2026-125283)

Record last updated .