CVE-2026-71620

HIGHPre-NVD 8.18.1—
EchelonGraph scoreHIGH confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-09-04. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 8.1; sources differ by 0.0.

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

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

File Upload vulnerability in Zhao-github ApiAdmin v.5.0.1 allows a remote attacker to execute arbitrary code via a crafted .php file

CVSS v3
8.1
EG Score
8.1(high)
EG Risk
37(Track)
EG Risk 37/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%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
37%
KEV
Not listed

Published

September 4, 2026

Last Modified

September 14, 2026

Advisory Details (1)

Auto-updated Sep 14, 2026
No patch confirmed yet.
generic

Notion

https://colorful-quill-4fe.notion.site/ApiAdmin-v5-0-1-rce-37fe5670300c80e3bc07da4694b5b953?pvs=73

Vendor Advisories for CVE-2026-71620(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 26× in last 7d / 41× 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-09-21 15:06 UTCGHSA enrichment
  2. 2026-09-21 02:47 UTCEG score recompute
  3. 2026-09-21 02:47 UTCGHSA enrichment
  4. 2026-09-20 20:16 UTCEPSS rescore
  5. 2026-09-20 14:48 UTCGHSA enrichment
  6. 2026-09-20 02:50 UTCEG score recompute
  7. 2026-09-20 02:50 UTCGHSA enrichment
  8. 2026-09-19 14:52 UTCGHSA enrichment
  9. 2026-09-19 02:53 UTCEG score recompute
  10. 2026-09-19 02:53 UTCGHSA enrichment
  11. 2026-09-18 19:28 UTCEPSS rescore
  12. 2026-09-18 14:56 UTCGHSA enrichment
  13. 2026-09-18 02:58 UTCEG score recompute
  14. 2026-09-18 02:58 UTCGHSA enrichment
  15. 2026-09-17 15:00 UTCGHSA enrichment
  16. 2026-09-17 03:01 UTCGHSA enrichment
  17. 2026-09-16 14:27 UTCEG score recompute
  18. 2026-09-16 14:27 UTCGHSA enrichment
  19. 2026-09-16 14:08 UTCEPSS rescore
  20. 2026-09-16 05:15 UTCEPSS rescore
  21. 2026-09-16 02:27 UTCGHSA enrichment
  22. 2026-09-15 14:29 UTCEG score recompute
  23. 2026-09-15 14:29 UTCGHSA enrichment
  24. 2026-09-15 03:12 UTCEPSS rescore
  25. 2026-09-15 02:31 UTCEG score recompute
Show 16 more
  1. 2026-09-15 02:31 UTCGHSA enrichment
  2. 2026-09-14 14:32 UTCGHSA enrichment
  3. 2026-09-14 13:30 UTCEG score recompute▲ 8.10
  4. 2026-09-14 13:30 UTCGHSA enrichment
  5. 2026-09-14 13:29 UTCMITRE cvelistV5CVSS v3 → 8.1 · severity → HIGH
  6. 2026-09-12 15:02 UTCEPSS rescore
  7. 2026-09-11 22:20 UTCGHSA enrichment
  8. 2026-09-11 14:53 UTCEPSS rescore
  9. 2026-09-10 09:35 UTCEPSS rescore
  10. 2026-09-08 19:59 UTCGHSA enrichment
  11. 2026-09-07 21:39 UTCEG score recompute
  12. 2026-09-07 21:39 UTCGHSA enrichment
  13. 2026-09-06 13:48 UTCEPSS rescore
  14. 2026-09-04 19:18 UTCNVD update
  15. 2026-09-04 19:09 UTCEG score recompute
  16. 2026-09-04 19:09 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-71620?
CVE-2026-71620 is a high vulnerability published on September 4, 2026. File Upload vulnerability in Zhao-github ApiAdmin v.5.0.1 allows a remote attacker to execute arbitrary code via a crafted .php file
When was CVE-2026-71620 disclosed?
CVE-2026-71620 was first published in the National Vulnerability Database on September 4, 2026, with the most recent update on September 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-71620 actively exploited?
CVE-2026-71620 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 63.0% of all scored CVEs.
What is the CVSS score of CVE-2026-71620?
CVE-2026-71620 has a CVSS v3.1 base score of 8.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-71620?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-71620, 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-71620

Explore →

Is Your Infrastructure Affected by CVE-2026-71620?

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

Start Free Scan →Browse All CVEs