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 — 3 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 17× in last 7d / 71× 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-18 23:52 UTCEG score recompute
  2. 2026-09-18 23:52 UTCGHSA enrichment
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 00:05 UTCEG score recompute
  5. 2026-09-18 00:05 UTCGHSA enrichment
  6. 2026-09-16 23:31 UTCEG score recompute
  7. 2026-09-16 23:31 UTCGHSA enrichment
  8. 2026-09-16 14:08 UTCEPSS rescore
  9. 2026-09-16 05:15 UTCEPSS rescore
  10. 2026-09-15 23:44 UTCEG score recompute
  11. 2026-09-15 23:44 UTCGHSA enrichment
  12. 2026-09-15 03:12 UTCEPSS rescore
  13. 2026-09-14 23:57 UTCGHSA enrichment
  14. 2026-09-14 00:10 UTCEG score recompute
  15. 2026-09-14 00:10 UTCGHSA enrichment
  16. 2026-09-13 00:23 UTCEG score recompute
  17. 2026-09-13 00:23 UTCGHSA enrichment
  18. 2026-09-12 15:02 UTCEPSS rescore
  19. 2026-09-12 00:36 UTCEG score recompute
  20. 2026-09-12 00:36 UTCGHSA enrichment
  21. 2026-09-11 14:53 UTCEPSS rescore
  22. 2026-09-11 00:50 UTCEG score recompute
  23. 2026-09-11 00:50 UTCGHSA enrichment
  24. 2026-09-10 09:35 UTCEPSS rescore
  25. 2026-09-10 01:04 UTCGHSA enrichment
Show 46 more
  1. 2026-09-09 01:17 UTCEG score recompute
  2. 2026-09-09 01:17 UTCGHSA enrichment
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 16:15 UTCEG score recompute
  5. 2026-09-07 16:15 UTCGHSA enrichment
  6. 2026-09-06 16:28 UTCEG score recompute
  7. 2026-09-06 16:28 UTCGHSA enrichment
  8. 2026-09-06 13:48 UTCEPSS rescore
  9. 2026-09-05 16:39 UTCEG score recompute
  10. 2026-09-05 16:38 UTCGHSA enrichment
  11. 2026-09-04 16:51 UTCEG score recompute
  12. 2026-09-04 16:50 UTCGHSA enrichment
  13. 2026-09-04 05:07 UTCEPSS rescore
  14. 2026-09-03 17:03 UTCGHSA enrichment
  15. 2026-09-02 17:16 UTCEG score recompute
  16. 2026-09-02 17:16 UTCGHSA enrichment
  17. 2026-09-02 14:12 UTCEPSS rescore
  18. 2026-09-01 17:29 UTCEG score recompute
  19. 2026-09-01 17:28 UTCGHSA enrichment
  20. 2026-09-01 13:54 UTCEPSS rescore
  21. 2026-09-01 04:40 UTCEPSS rescore
  22. 2026-09-01 04:40 UTCEPSS rescore
  23. 2026-08-31 17:41 UTCEG score recompute
  24. 2026-08-31 17:41 UTCGHSA enrichment
  25. 2026-08-30 19:18 UTCEPSS rescore
  26. 2026-08-30 19:17 UTCEPSS rescore
  27. 2026-08-30 17:38 UTCGHSA enrichment
  28. 2026-08-29 17:51 UTCEG score recompute
  29. 2026-08-29 17:51 UTCGHSA enrichment
  30. 2026-08-28 21:42 UTCEPSS rescore
  31. 2026-08-28 18:01 UTCGHSA enrichment
  32. 2026-08-27 18:11 UTCEG score recompute
  33. 2026-08-27 18:11 UTCGHSA enrichment
  34. 2026-08-27 14:25 UTCEPSS rescore
  35. 2026-08-26 17:23 UTCGHSA enrichment
  36. 2026-08-26 15:09 UTCEG score recompute
  37. 2026-08-26 15:09 UTCGHSA enrichment
  38. 2026-08-26 14:47 UTCEPSS rescore
  39. 2026-08-25 15:22 UTCEG score recompute
  40. 2026-08-25 15:22 UTCGHSA enrichment
  41. 2026-08-25 15:15 UTCEG score recompute
  42. 2026-08-25 15:15 UTCGHSA enrichment
  43. 2026-08-25 13:49 UTCEPSS rescore
  44. 2026-08-25 09:22 UTCEG score recompute
  45. 2026-08-25 09:07 UTCEG score recompute
  46. 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 88.8% 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