CVE-2026-34353 | OCaml up to 4.14.3 Bigarray.reshape integer overflow
VulDBArchived Mar 27, 2026✓ Full text saved
A vulnerability was found in OCaml up to 4.14.3 . It has been classified as problematic . This impacts the function Bigarray.reshape . The manipulation leads to integer overflow. This vulnerability is listed as CVE-2026-34353 . The attack must be carried out locally. There is no available exploit.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-353814 · CVE-2026-34353 · GCVE-0-2026-34353
OCAML UP TO 4.14.3 BIGARRAY.RESHAPE INTEGER OVERFLOW
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
4.2 $0-$5k 2.26+
Summaryinfo
A vulnerability was found in OCaml up to 4.14.3. It has been declared as problematic. Affected is the function Bigarray.reshape. The manipulation results in integer overflow. This vulnerability is cataloged as CVE-2026-34353. The attack must be initiated from a local position. There is no exploit available.
Detailsinfo
A vulnerability was found in OCaml up to 4.14.3. It has been classified as problematic. Affected is the function Bigarray.reshape. The manipulation with an unknown input leads to a integer overflow vulnerability. CWE is classifying the issue as CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control. This is going to have an impact on confidentiality. CVE summarizes:
In OCaml through 4.14.3, Bigarray.reshape allows an integer overflow, and resultant reading of arbitrary memory, when untrusted data is processed.
The advisory is available at github.com. This vulnerability is traded as CVE-2026-34353 since 03/27/2026. The exploitability is told to be difficult. Local access is required to approach this attack. Technical details are known, but there is no available exploit.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Productinfo
Name
OCaml
Version
4.14.0
4.14.1
4.14.2
4.14.3
Website
Product: https://github.com/ocaml/ocaml/
CPE 2.3info
🔒
🔒
🔒
CPE 2.2info
🔒
🔒
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv3info
VulDB Meta Base Score: 4.2
VulDB Meta Temp Score: 4.2
VulDB Base Score: 2.5
VulDB Temp Score: 2.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.9
CNA Vector (MITRE): 🔒
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Integer overflow
CWE: CWE-190 / CWE-189
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: no mitigation known
Status: 🔍
0-Day Time: 🔒
Timelineinfo
03/27/2026 Advisory disclosed
03/27/2026 +0 days CVE reserved
03/27/2026 +0 days VulDB entry created
03/27/2026 +0 days VulDB entry last update
Sourcesinfo
Product: github.com
Advisory: github.com
Status: Confirmed
CVE: CVE-2026-34353 (🔒)
GCVE (CVE): GCVE-0-2026-34353
GCVE (VulDB): GCVE-100-353814
Entryinfo
Created: 03/27/2026 07:26
Changes: 03/27/2026 07:26 (60)
Complete: 🔍
Cache ID: 99:419:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸