← Back
CVE-2026-67550
medium
CVSS 5.7
Out-of-Bounds Read in re2 (CVE-2026-67550)
Summary
vulnerability in re2 (CVE-2026-67550). Risk of unauthorized operations or information disclosure. Exploitable via ``re2``. Mitigation: upgrade to `1.25.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-67550** has been found in re2.
Attackers can target a specific entry point like ``re2`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.7/10.
What to do: upgrade re2 to **1.25.1** or later.
If unsure, ask your IT team or search "re2 CVE-2026-67550" on the vendor's site.
CVE-2026-67550 (re2) — CWE-125 / CVSS v3 5.7
Attack vector: local / unauthenticated / no user interaction
Attack surface: `re2` / `lastIndex` / `setIndex` / `getUtf16PositionByCounter`
Patched: `1.25.1` — 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
**out-of-bounds read** (CWE-125) exists in re2. Attackers reach the vulnerable code path via ``re2`` without authentication.
📍 Affected scope
re2 — . Attack surface: `re2` / `lastIndex` / `setIndex` / `getUtf16PositionByCounter`.
🔥 Severity
Severity: Medium (CVSS 5.7/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.25.1**.
🛡️ 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 're2' .` 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
-
1Identify exposure identify
grep -r 're2' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `re2` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade re2 to 1.25.1ステージング環境で 1.25.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
re2
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.25.2"}]}]