How severe is CVE-2022-26661?

CVE-2022-26661 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-26661?

CVE-2022-26661 affects the following packages: trytond (PyPI), trytond (PyPI), trytond (PyPI), proteus (PyPI), proteus (PyPI), proteus (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2022-26661?

Update trytond to 5.0.46 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-26661 is resolved across your whole dependency graph.

How do I detect CVE-2022-26661 in my PyPI dependencies?

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

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

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2022-26661 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2022-26661, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-26661?

CVE-2022-26661 has an EPSS (Exploit Prediction Scoring System) score of 1.4%, placing it in the 72th 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-2022-26661?

CVE-2022-26661 is classified as XML External Entity (XXE) (CWE-611). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-26661 published, and has it been updated?

CVE-2022-26661 was published on March 7, 2022 and was last updated on October 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

MEDIUM severity

CVE-2022-26661 — trytond

MEDIUM

CVE-2022-26661 is a medium-severity (CVSS 6.5) XML External Entity (XXE) vulnerability in trytond. 1 public exploit reference exists, so weaponization risk is real. A fix is available for trytond — see the affected versions and patch details below.

Improper Restriction of XML External Entity Reference in trytond and proteus

Also known asGHSA-cj78-rgw3-4h5pPYSEC-2022-43170PYSEC-2026-3391PYSEC-2026-740

Published

Mar 7, 2022

Updated

Oct 8, 2026

Affected

6 pkgs

Patched

6 / 6

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

1.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs72th percentile — riskier than 72% of all scored CVEsHighest risk

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

How urgent is this, really

CVE-2022-26661 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

6 pkgs affected

🐍trytond🐍trytond🐍trytond🐍proteus🐍proteus🐍proteus

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

Description

An XXE issue was discovered in Tryton Application Platform (Server) 5.x through 5.0.45, 6.x through 6.0.15, and 6.1.x and 6.2.x through 6.2.5, and Tryton Application Platform (Command Line Client (proteus)) 5.x through 5.0.11, 6.x through 6.0.4, and 6.1.x and 6.2.x through 6.2.1. An authenticated user can make the server parse a crafted XML SEPA file to access arbitrary files on the system.

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`trytond`	≥ 5.0.0&&< 5.0.46	5.0.46`pip install --upgrade 'trytond==5.0.46'`
🐍PyPI	`trytond`	≥ 6.0.0&&< 6.0.16	6.0.16`pip install --upgrade 'trytond==6.0.16'`
🐍PyPI	`trytond`	≥ 6.1.0&&< 6.2.6	6.2.6`pip install --upgrade 'trytond==6.2.6'`
🐍PyPI	`proteus`	≥ 5.0.0&&< 5.0.12	5.0.12`pip install --upgrade 'proteus==5.0.12'`
🐍PyPI	`proteus`	≥ 6.0.0&&< 6.0.5	6.0.5`pip install --upgrade 'proteus==6.0.5'`
🐍PyPI	`proteus`	≥ 6.1.0&&< 6.2.2	6.2.2`pip install --upgrade 'proteus==6.2.2'`

Affected Products

3 products · 9 configurations

debian linuxdebian

3 versions

9.010.011.0

Application

proteustryton

≥ 6.2.0 && < 6.2.2

range

Application

trytondtryton

≥ 6.2.0 && < 6.2.6

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

An XXE issue was discovered in Tryton Application Platform (Server) 5.x …

bugs.tryton.orgNVDMar 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for trytond, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update trytond to 5.0.46 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-26661 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2022-26661 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

CWE Classification

CWE-611XML External Entity (XXE)

Weaponization

No known public exploit tooling found.

Timeline

Disclosed

Mar 7, 2022

First exploit

Mar 18, 2022

Last updated

Oct 8, 2026

Identifiers

CVE-2022-26661

GHSA-cj78-rgw3-4h5p

PYSEC-2022-43170

PYSEC-2026-3391

PYSEC-2026-740

References

Advisorygithub.com Advisorynvd.nist.gov Advisorydebian.org Advisorydebian.org Articlelists.debian.org Articlelists.debian.org Webbugs.tryton.org Webdiscuss.tryton.org Webfoss.heptapod.net Packagehg.tryton.org

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs affecting trytond are rated as high or higher (top: high).

CVE-2025-66424CVE-2025-66422CVE-2025-66423CVE-2016-1241CVE-2016-1242CVE-2013-4510CVE-2015-0861CVE-2014-6633

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 8, 2026

CVE-2022-26661 — trytond

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2022-26661 in your dependencies?