TensorFlow v2.18.0 was discovered to output random results when compiling Embedding, leading to unexpected behavior in the application.

published 2025-09-25 13 mo ago modified 2026-11-05 3 d ago also BIT-tensorflow-2025-55556 , EUVD-2025-31129

cvss: 6.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.2%; EPSS 0.2% chance of exploitation in 30 days, percentile 6%
public exploits: 0; none known

Patch / fix

fixed in 1

bitnami tensorflow 2.18.1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-55556 updated 2026-06-27 cvss 6.5

tensorflow: Tensorflow inconsistent results

Red Hat OpenShift AI (RHOAI) rhoai/odh-modelmesh-runtime-adapter-rhel8, rhoai/odh-modelmesh-runtime-adapter-rhel9
affected: workaround, no fix available “Fix deferred”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 13 mo ago (2025-09-26)

Exploit prediction

0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

github.com https://github.com/tensorflow/tensorflow/issues/82317 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CISA ADP	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
CNA	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
OSV	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

Affected packages

ecosystem	package	affected	fixed in
bitnami	tensorflow	>=2.18.0, <2.18.1	2.18.1

Classification

Weakness

CWE-506 Embedded Malicious Code

References

github.com /tensorflow/tensorflow/issues/82317
exploit, issue-tracking, evidence
gist.github.com /shaoyuyoung/0e7d2a586297ae9c8ed14d8706749efc
third-party-advisory, advisory
nvd.nist.gov /vuln/detail/CVE-2025-55556
web

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary