CVE-2026-77130Disclosure

LOWCVSS 5.3 · MEDIUM

Signal is active with 2 mentions in latest observed window

Immediate actions

Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD description

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.

Back to dashboard

0.0/ 10 priority

Sources & remediation

Other references

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

Weakness type (CWE)

CWE-613

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

NONE

Threat summary

2 mentions across 1 observed day

What's happening

Technical details provided in 2 signals
Disclosure: 1 classified signal
General: 1 classified signal
2 total mentions across 1 day

Deep dive

Activity timeline2 mentions / 1d

Signal classification2 categories

Disclosure

150.0%

General

150.0%

Referenced assets2 URLs

By indicator

Full discourse2 posts

Infoflowcloud@infoflowcloud45d
General
🚨*CVE* CVE-2026-77130 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 exp… https://www.cve.org/CVERecord?id=CVE-2026-77130 ----- Traducción: CVE-2026-77130 La … https://infoflow.cloud`
Post summary
The tweet only supplies a brief technical description of CVE‑2026‑77130 and a link to the CVE record; it offers no PoC, exploit, patch info, or evidence of active exploitation.
0000037
102 followersView on X
CVE@CVEnew45d
Disclosure
CVE-2026-77130 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 exp… https://www.cve.org/CVERecord?id=CVE-2026-77130
Post summary
CVE-2026-77130 identifies a flaw where an extension neglects to check JWT expiration, enabling attackers with valid API keys to authenticate past the token’s intended lifespan.
00000864
58.0K followersView on X

Explore more

Back to dashboard