CVE-2023-33976: TensorFlow segfault in array_ops.upper_bound
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.43% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: cbl2 tensorflow 2.11.1-2 on CBL Mariner 2.0 2.11.1-2; cbl2 tensorflow 2.11.1-2 on CBL-Mariner 2.0 2.11.1-2.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to cbl2 tensorflow 2.11.1-2 on CBL Mariner 2.0 2.11.1-2; cbl2 tensorflow 2.11.1-2 on CBL-Mariner 2.0 2.11.1-2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
TensorFlow is an end-to-end open source platform for machine learning. `array_ops.upper_bound` causes a segfault when not given a rank 2 tensor. The fix will be included in TensorFlow 2.13 and will also cherrypick this commit on TensorFlow 2.12.
- Published
- Jul 30, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.4% · 36th percentile
- CWE
- CWE-190
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.5
- CNA · GitHub_M
- 7.5
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| tensorflow | cpe:2.3:a:google:tensorflow |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- google tensorflowbefore 2.13.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
tensorflow tensorflow
- < 2.13.0affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| PyPI | tensorflow | before 2.12.1 | 2.12.1 |
| PyPI | tensorflow-cpu | before 2.12.1 | 2.12.1 |
| PyPI | tensorflow-gpu | before 2.12.1 | 2.12.1 |
Same product
google: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-25668TensorFlow vulnerable to heap out-of-buffer read in the QuantizeAndDequantize operation39Monitor
- CVE-2023-25664TensorFlow vulnerable to Heap Buffer Overflow in AvgPoolGrad39Monitor
- CVE-2022-41900FractionalMaxPool and FractionalAVGPool heap out-of-bounds acess in Tensorflow39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2023-27579Mar 24, 2023 · TensorFlow has Floating Point Exception in TFLite in conv kernel30Monitor
- ← EarlierCVE-2023-25661Mar 27, 2023 · Denial of Service in TensorFlow26Monitor
- Later →CVE-2025-55556Sep 25, 2025 · TensorFlow v2.18.0 was discovered to output random results when compiling Embedding, leading to unexpected behavior in the application.26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| cbl2 tensorflow 2.11.1-2 on CBL Mariner 2.0 | 2.11.1-2 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 tensorflow 2.11.1-2 on CBL-Mariner 2.0 | 2.11.1-2 · CBL-Mariner Releases | Microsoft (MSRC) |
| PyPI:tensorflow | 2.12.1 | Package registry (OSV) |
| PyPI:tensorflow-cpu | 2.12.1 | Package registry (OSV) |
| PyPI:tensorflow-gpu | 2.12.1 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2023-25662494 days apartTensorFlow vulnerable to integer overflow in EditDistance30Monitor
- CVE-2023-25667494 days apartTensorFlow vulnerable to segfault when opening multiframe gif30Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-1131 · Aug 1, 2024(TensorFlow Güvenlik Zafiyeti)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-190 · Integer Overflow or WraparoundCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.