Vulnerability in ocaml (CVE-2026-34353)

Summary

vulnerability in ocaml (CVE-2026-34353). Confidential information can be exposed externally. Exploitable via ``caml_ba_reshape``. Mitigation: upgrade to `4.14.4, 1ec6b6e8ef9d30fc1d8bac71a6646c2ef78ea90b` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-34353** has been found in ocaml. Attackers can target a specific entry point like ``caml_ba_reshape`` over the network to misuse the product. Confidential information can be exposed externally. CVSS score: ?/10. What to do: upgrade ocaml to **4.14.4, 1ec6b6e8ef9d30fc1d8bac71a6646c2ef78ea90b** or later. If unsure, ask your IT team or search "ocaml CVE-2026-34353" on the vendor's site.

CVE-2026-34353 (ocaml) — Attack vector: local / no user interaction Attack surface: `caml_ba_reshape` / `Bigarray.reshape` / `reshape_N` Patched: `4.14.4, 1ec6b6e8ef9d30fc1d8bac71a6646c2ef78ea90b` — apply immediately Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs. Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

**A vulnerability** (unclassified) exists in ocaml. Attackers reach the vulnerable code path via ``caml_ba_reshape`` without authentication.

📍 Affected scope

ocaml — . Attack surface: `caml_ba_reshape` / `Bigarray.reshape` / `reshape_N`.

🔥 Severity

Severity: ?. Confidential information can be exposed externally

🔧 How to fix

Update to **4.14.4, 1ec6b6e8ef9d30fc1d8bac71a6646c2ef78ea90b**.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'ocaml' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'ocaml' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `ocaml` を grep し、稼働しているサービス・バージョンを把握する。
6
Apply patch patch
```
Upgrade ocaml to 4.14.4, 1ec6b6e8ef9d30fc1d8bac71a6646c2ef78ea90b
```
ステージング環境で 4.14.4, 1ec6b6e8ef9d30fc1d8bac71a6646c2ef78ea90b に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
7
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

opam ocaml

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.14.4"}]},{"repo":"https:\/\/github.com\/ocaml\/ocaml","type":"GIT","events":[{"introduced":"0"},{"fixed":"1ec6b6e8ef9d30fc1d8bac71a6646c2ef78ea90b"}]}]

References

patch https://github.com/ocaml/ocaml/pull/14691
report https://github.com/ocaml/ocaml/issues/14655