NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

CVE-2025-66421 — tryton-sao

MEDIUM

CVE-2025-66421 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in tryton-sao. A fix is available for tryton-sao — see the affected versions and patch details below.

Tryton sao allows XSS because it does not escape completion values

Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed
Exploitation data as of Nov 10, 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-2025-66421.

EPSS Exploitation Probability

via FIRST.org ↗
0.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs8th percentile — riskier than 8% of all scored CVEsHighest risk
0.00%0.23%0.45%0.68%0.0%0.2%May 26Aug 26Nov 26

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected
📦tryton-sao📦tryton-sao📦tryton-sao📦tryton-sao

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

Description

Tryton sao (aka tryton-sao) before 7.6.11 allows XSS because it does not escape completion values. This is fixed in 7.6.11, 7.4.21, 7.0.40, and 6.0.69.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
📦npmtryton-sao≥ 7.5.0&&< 7.6.117.6.11npm install tryton-sao@7.6.11
📦npmtryton-sao≥ 7.1.0&&< 7.4.217.4.21npm install tryton-sao@7.4.21
📦npmtryton-sao≥ 7.0.0&&< 7.0.407.0.40npm install tryton-sao@7.0.40
📦npmtryton-saoall versions6.0.69npm install tryton-sao@6.0.69

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update tryton-sao to 7.6.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-66421 is resolved across your whole dependency graph.

  3. Workarounds

    Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

Tryton sao (aka tryton-sao) before 7.6.11 allows XSS because it does not escape completion values. This is fixed in 7.6.11, 7.4.21, 7.0.40, and 6.0.69.
O3 Security · Impact-Aware SCA

Is CVE-2025-66421 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works