TensorFlow v2.18.0 was discovered to output random results when compiling Embedding, leading to unexpected behavior in the application.
CVE-2025-55556
Score 6.5 from GitHub Security Advisory published 2025-09-25. NVD baseline CVSS 6.5; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(medium)
- EG Risk
- 29(Track)EG Risk 29/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity65% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 7%
- KEV
- Not listed
Published
September 25, 2025
Last Modified
October 3, 2025
References (2)
Affected Packages
(1 across 1 ecosystem)
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| tensorflow | 1.10.1+dfsg-A1 ... 2.3.1-1 (7 versions) | — | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Frequently asked(5)
What is CVE-2025-55556?
When was CVE-2025-55556 disclosed?
Is CVE-2025-55556 actively exploited?
What is the CVSS score of CVE-2025-55556?
How do I remediate CVE-2025-55556?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-55556
Is Your Infrastructure Affected by CVE-2025-55556?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.