CVE-2026-113459 Sensitive Data Exposure in extension "TYPO3 AI Integration Extension" (ns_t3ai)
High 7.1
Published
Updated
Check this codebase for CVE-2026-113459 and fix it if it is affected.
What it is: CVE-2026-113459 is a high-severity vulnerability in Extension "TYPO3 AI Integration Extension", published on 20 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-113459 in the wild and no public exploit code.
Affected product: Extension "TYPO3 AI Integration Extension". 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-113459/ (Markdown: https://insights.sbomify.com/CVE-2026-113459/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-113459?
CVE-2026-113459 is a high-severity vulnerability in Extension "TYPO3 AI Integration Extension", published on 20 Oct 2026.
Official 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.
Weakness: CWE-201
Which versions are affected by CVE-2026-113459?
How do I fix CVE-2026-113459?
No fix has been published for CVE-2026-113459 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-113459 being exploited?
There is no known exploitation of CVE-2026-113459 in the wild and no public exploit code.
Sources
Also known as GHSA-7546-2qgp-jfhx.