CVE-2025-0649: Stack Exhaustion In Tensorflow Serving
First published: Tue May 06 2025(Updated: )
Incorrect JSON input stringification in Google's Tensorflow serving versions up to 2.18.0 allows for potentially unbounded recursion leading to server crash.
Credit: cve-coordination@google.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| TensorFlow Serving | <=2.18.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2025-0649?
CVE-2025-0649 is considered a high severity vulnerability due to its potential to cause server crashes.
How do I fix CVE-2025-0649?
To fix CVE-2025-0649, upgrade Google TensorFlow Serving to version 2.19.0 or later.
What causes CVE-2025-0649?
CVE-2025-0649 is caused by incorrect JSON input stringification that leads to potentially unbounded recursion.
Which versions of TensorFlow Serving are affected by CVE-2025-0649?
CVE-2025-0649 affects Google TensorFlow Serving versions up to and including 2.18.0.
What could happen if I don't address CVE-2025-0649?
If CVE-2025-0649 is not addressed, it could lead to server crashes impacting service availability.
- collector/mitre-cve
- source/MITRE
- agent/references
- agent/weakness
- agent/title
- agent/first-publish-date
- agent/description
- agent/type
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- agent/softwarecombine
- collector/nvd-api
- source/NVD
- agent/author
- agent/last-modified-date
- agent/severity
- agent/source
- agent/tags
- agent/event
- vendor/google
- canonical/tensorflow serving