CVE-2026-75005

HIGHNVD 7.57.5
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-27. NVD baseline CVSS 7.5; sources differ by 0.0.

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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Inefficient Algorithmic Complexity vulnerability in Apache APISIX.

A single small request can pin a gateway worker at 100% CPU for an extended period in graphql-limit-count routes.

This issue affects Apache APISIX: 3.17.0.

Users are recommended to upgrade to version 3.18.0, which fixes the issue.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
53%
KEV
Not listed

Published

August 27, 2026

Last Modified

August 28, 2026

Advisory Details (1)

Auto-updated Aug 27, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-75005(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

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

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-29 21:18 UTCGHSA enrichment
  3. 2026-08-29 09:02 UTCEG score recompute
  4. 2026-08-29 09:02 UTCGHSA enrichment
  5. 2026-08-28 21:42 UTCEPSS rescore
  6. 2026-08-28 20:45 UTCEG score recompute 1.20
  7. 2026-08-28 20:45 UTCGHSA enrichment
  8. 2026-08-28 20:44 UTCNVD updateCVSS v3 → 7.5
  9. 2026-08-28 15:46 UTCGHSA enrichment
  10. 2026-08-28 14:09 UTCGHSA enrichment
  11. 2026-08-28 01:48 UTCEG score recompute
  12. 2026-08-28 01:48 UTCGHSA enrichment
  13. 2026-08-27 14:25 UTCEPSS rescore
  14. 2026-08-27 13:32 UTCEG score recompute
  15. 2026-08-27 13:32 UTCGHSA enrichment
  16. 2026-08-27 12:59 UTCEG score recompute
  17. 2026-08-27 12:59 UTCGHSA enrichment
  18. 2026-08-27 10:26 UTCEG score recompute
  19. 2026-08-27 09:24 UTCEG score recompute
  20. 2026-08-27 09:23 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-75005?
CVE-2026-75005 is a high vulnerability published on August 27, 2026. Inefficient Algorithmic Complexity vulnerability in Apache APISIX. A single small request can pin a gateway worker at 100% CPU for an extended period in graphql-limit-count routes. This issue affects Apache APISIX: 3.17.0. Users are recommended to upgrade to version 3.18.0, which fixes the issue.
When was CVE-2026-75005 disclosed?
CVE-2026-75005 was first published in the National Vulnerability Database on August 27, 2026, with the most recent update on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-75005 actively exploited?
CVE-2026-75005 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 46.5% of all scored CVEs.
What is the CVSS score of CVE-2026-75005?
CVE-2026-75005 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-75005?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-75005, 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-75005

Explore →

Is Your Infrastructure Affected by CVE-2026-75005?

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