How severe is CVE-2026-8827?

No CVSS score has been assigned to CVE-2026-8827 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-8827?

CVE-2026-8827 affects the following packages: friendsoftypo3/tt-address (Packagist), friendsoftypo3/tt-address (Packagist), friendsoftypo3/tt-address (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2026-8827?

Update friendsoftypo3/tt-address to 10.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-8827 is resolved across your whole dependency graph.

How do I detect CVE-2026-8827 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for friendsoftypo3/tt-address, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-8827 if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is CVE-2026-8827 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-8827 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-8827?

CVE-2026-8827 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 30th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-8827?

CVE-2026-8827 is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2026-8827 published, and has it been updated?

CVE-2026-8827 was published on May 19, 2026 and was last updated on August 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

CVE-2026-8827 — friendsoftypo3/tt-address

CVE-2026-8827 is a SQL Injection vulnerability in friendsoftypo3/tt-address. A fix is available for friendsoftypo3/tt-address — see the affected versions and patch details below.

SQL Injection in extension "Address List" (tt_address)

Also known asGHSA-3h52-6v6j-6wwv

Published

May 19, 2026

Updated

Aug 12, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Sep 27, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-8827.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs30th percentile — riskier than 30% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

3 pkgs affected

🐘friendsoftypo3/tt-address🐘friendsoftypo3/tt-address🐘friendsoftypo3/tt-address

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

In the TYPO3 extension tt_address, the AddressRepository::getSqlQuery() method constructs a database query without properly sanitizing user input, leading to SQL Injection. The method is not invoked anywhere within the extension itself and therefore poses no direct risk in a default installation. However, custom extensions that call this method with untrusted input would expose the site to SQL injection. This has been patched in version 8.1.2, 9.1.1, and 10.0.1.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`friendsoftypo3/tt-address`	≥ 10.0.0&&< 10.0.1	10.0.1`composer require friendsoftypo3/tt-address:^10.0.1`
🐘Packagist	`friendsoftypo3/tt-address`	≥ 9.0.0&&< 9.1.1	9.1.1`composer require friendsoftypo3/tt-address:^9.1.1`
🐘Packagist	`friendsoftypo3/tt-address`	all versions	8.1.2`composer require friendsoftypo3/tt-address:^8.1.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for friendsoftypo3/tt-address, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update friendsoftypo3/tt-address to 10.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-8827 is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Frequently Asked Questions

In the TYPO3 extension `tt_address`, the `AddressRepository::getSqlQuery()` method constructs a database query without properly sanitizing user input, leading to SQL Injection. The method is not invoked anywhere within the extension itself and therefore poses no direct risk in a default installation. However, custom extensions that call this method with untrusted input would expose the site to SQL injection. This has been patched in version 8.1.2, 9.1.1, and 10.0.1.

O3 Security · Impact-Aware SCA

Is CVE-2026-8827 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works