# CVE-2026-77130: TYPO3 SYSSY insufficient JWT token expiration validation

Source: https://junglewise.ai/threats/cve-2026-77130-typo3-syssy-insufficient-jwt-token-expiration-validation  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-08-25. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

CVE-2026-77130 · Severity: info · CVSS 5.7 · Published 2026-08-25

SYSSY is a TYPO3 extension that monitors and secures TYPO3 installations. It fails to properly validate JWT token expiration, allowing an attacker who possesses a valid API key to authenticate using expired tokens and potentially maintain unauthorized access. This requires the attacker to already have obtained the API key through other means.

Vendors: [Typo3](https://junglewise.ai/threats/vendors/typo3).

## Quick answers

**Is CVE-2026-77130 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-77130 being exploited in the wild.

**How severe is CVE-2026-77130?** Informational severity, with a CVSS score of 5.7, published 25 August 2026.

**Which products and versions are affected?** Typo3 SYSSY 3.0.5 and below.

**Is there a fix for CVE-2026-77130?** A patch was published on 2026-08-25: Version 3.0.6 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-77130 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-77130?** Check whether you run Typo3 SYSSY at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The extension implements JWT token validation but does not properly check token expiration timestamps, allowing expired tokens to be accepted for authentication. The vulnerability is classified as CWE-613 (Insufficient Session Expiration). Attack requires network access to the extension's API endpoint and a valid API key obtained by the attacker through prior compromise or disclosure. An authenticated attacker can use an expired token to authenticate and perform actions as if the token were still valid. A patch is available in version 3.0.6.

## Affected products

- TYPO3 SYSSY 3.0.5 and below

## Timeline

- 2026-08-25: disclosed
- 2026-08-25: patched: Version 3.0.6 released

## References

- [https://packagist.org/](https://packagist.org/)
- [https://typo3.org/security/advisory/typo3-ext-sa-2026-015](https://typo3.org/security/advisory/typo3-ext-sa-2026-015)