Vulnerability in libsoup3 (OESA-2026-2337)

Summary

vulnerability in libsoup3 (OESA-2026-2337). Risk of unauthorized operations or information disclosure. Exploitable via `Authorization header`. Mitigation: upgrade to `3.4.5-13.oe2403` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **OESA-2026-2337** has been found in libsoup3. Attackers can target a specific entry point like `Authorization header` over the network to misuse the product. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade libsoup3 to **3.4.5-13.oe2403** or later. If unsure, ask your IT team or search "libsoup3 OESA-2026-2337" on the vendor's site.

OESA-2026-2337 (libsoup3) — Attack surface: Authorization header / Host header Patched: `3.4.5-13.oe2403` — 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 libsoup3. Attackers reach the vulnerable code path via `Authorization header` without authentication.

📍 Affected scope

libsoup3 — . Attack surface: Authorization header / Host header.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure

🔧 How to fix

Update to **3.4.5-13.oe2403**.

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

Affected packages

openEuler:24.03-LTS libsoup3

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.4.5-13.oe2403"}]}]

References

advisory https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-2337
advisory https://nvd.nist.gov/vuln/detail/CVE-2025-12105
advisory https://nvd.nist.gov/vuln/detail/CVE-2025-14523
advisory https://nvd.nist.gov/vuln/detail/CVE-2025-46420
advisory https://nvd.nist.gov/vuln/detail/CVE-2025-4945
advisory https://nvd.nist.gov/vuln/detail/CVE-2025-4948
advisory https://nvd.nist.gov/vuln/detail/CVE-2025-4969
advisory https://nvd.nist.gov/vuln/detail/CVE-2026-0716
advisory https://nvd.nist.gov/vuln/detail/CVE-2026-1467
advisory https://nvd.nist.gov/vuln/detail/CVE-2026-1536
advisory https://nvd.nist.gov/vuln/detail/CVE-2026-1539