# CVE-2026-77131: Cleartext Transmission of Sensitive Information in extension "SYSSY - TYPO3 Monitoring & Security Checks" (syssy)

> Attackers with API keys can read sensitive system information transmitted in cleartext when OpenSSL is unavailable on the server.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Aug 2026
- **Updated:** 25 Aug 2026
- **Also known as:** GHSA-8j7q-247m-7f82

## What is CVE-2026-77131?

CVE-2026-77131 is a medium-severity vulnerability in Extension "SYSSY - TYPO3 Monitoring & Security Checks", published on 25 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

When OpenSSL is unavailable on the server, the extension transmits TYPO3 system information in cleartext instead of encrypting it. Exploitation requires the attacker to already be in control of the SYSSY project's API key.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

## Which versions are affected by CVE-2026-77131?


## How do I fix CVE-2026-77131?

No fix has been published for CVE-2026-77131 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-77131 being exploited?

There is no known exploitation of CVE-2026-77131 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-77131 and fix it if it is affected.

What it is: CVE-2026-77131 is a medium-severity vulnerability in Extension "SYSSY - TYPO3 Monitoring & Security Checks", published on 25 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-77131 in the wild and no public exploit code.

Affected product: Extension "SYSSY - TYPO3 Monitoring & Security Checks". No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-77131/ (Markdown: https://insights.sbomify.com/CVE-2026-77131/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-77131
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-77131
- OSV: https://osv.dev/vulnerability/CVE-2026-77131

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-77131/
Summaries are generated and may contain mistakes; the official description above is the record.