VulnerabilityPublished 12 Mar 2026

CVE-2026-32251: tolgee-platform · XML External Entity (XXE)

Affects tolgee-platformSource CVE Database V5

Compare

Not known to be exploited · CVSS 9.3 Critical : upgrade to 3.166.3 as a priority.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score

9.3Critical

How severe the flaw is on the 0–10 CVSS scale.

Contested

Critical score, yet low EPSS after six months

EPSS: 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.166.3

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: High
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: High
Subsequent system integrity: High
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: High: There is a total loss of confidentiality, resulting in all resources within the Subsequent System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Subsequent system integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the Subsequent System. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the Subsequent System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade tolgee-platform and tolgee/tolgee-platform to 3.166.3.

Affected software

Product	Affected	Fixed in
tolgeetolgee-platform	Affected <3.166.3	Fixed in 3.166.3
GitHubtolgee/tolgee-platform`pkg:github/tolgee/tolgee-platform`Other threats	Affected <3.166.3	Fixed in 3.166.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-32251, organizations should immediately upgrade tolgee-platform to version 3.166.3 or later, where the XML parser properly disables external entity processing. Until the upgrade is applied, restrict the ability to import translation files to a minimal set of trusted, authenticated users to reduce the attack surface. Implement strict access controls and monitor import activities for suspicious or anomalous file uploads. Employ network segmentation and firewall rules to limit tolgee-platform server access to internal services, reducing the impact of SSRF attacks. Additionally, conduct regular audits of server file permissions and logs to detect unauthorized file access attempts. Consider deploying runtime application self-protection (RASP) or web application firewalls (WAFs) with rules targeting XXE payloads to provide an additional layer of defense. Finally, educate developers and administrators about secure XML parsing practices and the risks of enabling external entity processing.

Description

CVE-2026-32251 is a critical XML External Entity (XXE) vulnerability in tolgee-platform versions prior to 3.166.3. The issue arises because the XML parsers used for importing Android XML and . resx translation files do not disable external entity processing. An authenticated user with permission to import translation files can exploit this flaw to read arbitrary files on the server and perform server-side requests to internal services, potentially exposing sensitive data and internal network resources. The vulnerability has a CVSS 4.0 score of 9.3, indicating critical severity, and requires no user interaction or privileges beyond authentication. Although no known exploits are currently reported in the wild, the impact could be severe if weaponized.

Impact

The impact of CVE-2026-32251 is substantial for organizations using tolgee-platform versions prior to 3.166.3. Exploitation allows an authenticated user to read arbitrary files on the server, potentially exposing sensitive configuration files, credentials, or proprietary data. Additionally, the ability to make server-side requests to internal services can facilitate further network reconnaissance, lateral movement, or exploitation of internal-only services not exposed externally. This can lead to significant confidentiality breaches and compromise of internal infrastructure. Since tolgee-platform is used for localization management, organizations with sensitive intellectual property or regulated data in their translation files or internal systems are at heightened risk. The vulnerability's ease of exploitation—requiring only authenticated access and no user interaction—means insider threats or compromised user accounts can quickly lead to severe data breaches. The absence of known exploits in the wild currently reduces immediate risk but does not diminish the criticality of patching. Failure to remediate could result in data leakage, disruption of localization workflows, and potential compliance violations.

CWE-611Improper Restriction of XML External Entity Reference (opens in a new tab)
Base weaknessOWASP Top 10 A02:2025: Security Misconfiguration (opens in a new tab)
The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.
Implementation · System Configuration
Many XML parsers and validators can be configured to disable external entity expansion.
OWASP Cheat Sheets
Deserialization (opens in a new tab)
XML Security (opens in a new tab)
XML External Entity Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V5.5.2 (opens in a new tab)
Attack patterns
Data Serialization External Entities Blowup (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 20 Mar 2026, 02:35 UTC

WeaknessesCWE-611

Technical details

References

Community reviews

Related threats