CVE-2026-77130

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 89% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 4 sources updated this week
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

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

The extension fails to properly validate the expiration of a client-supplied JWT token, allowing an attacker in control of a valid API key to authenticate with an expired token. Exploitation requires the attacker to already be in control of the SYSSY project's API key.

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

Published

August 25, 2026

Last Modified

August 26, 2026

Advisory Details (1)

Auto-updated Aug 25, 2026
No patch confirmed yet.
generic

TYPO3-EXT-SA-2026-015: Multiple Vulnerabilities in extension "SYSSY - TYPO3 Monitoring & Security Checks" (syssy) - TYPO3 News

https://typo3.org/security/advisory/typo3-ext-sa-2026-015

Vendor Advisories for CVE-2026-77130(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 15× in last 7d / 15× 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-27 18:11 UTCEG score recompute
  2. 2026-08-27 18:11 UTCGHSA enrichment
  3. 2026-08-27 14:25 UTCEPSS rescore
  4. 2026-08-26 17:23 UTCGHSA enrichment
  5. 2026-08-26 15:09 UTCEG score recompute
  6. 2026-08-26 15:09 UTCGHSA enrichment
  7. 2026-08-26 14:47 UTCEPSS rescore
  8. 2026-08-25 15:22 UTCEG score recompute
  9. 2026-08-25 15:22 UTCGHSA enrichment
  10. 2026-08-25 15:15 UTCEG score recompute
  11. 2026-08-25 15:15 UTCGHSA enrichment
  12. 2026-08-25 13:49 UTCEPSS rescore
  13. 2026-08-25 09:22 UTCEG score recompute
  14. 2026-08-25 09:07 UTCEG score recompute
  15. 2026-08-25 09:06 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-77130?
CVE-2026-77130 is a medium vulnerability published on August 25, 2026. The extension fails to properly validate the expiration of a client-supplied JWT token, allowing an attacker in control of a valid API key to authenticate with an expired token. Exploitation requires the attacker to already be in control of the SYSSY project's API key.
When was CVE-2026-77130 disclosed?
CVE-2026-77130 was first published in the National Vulnerability Database on August 25, 2026, with the most recent update on August 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-77130 actively exploited?
CVE-2026-77130 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 89.3% of all scored CVEs.
What is the CVSS score of CVE-2026-77130?
CVE-2026-77130 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-77130?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-77130, 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-77130

Explore →

Is Your Infrastructure Affected by CVE-2026-77130?

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

Start Free Scan →Browse All CVEs