← Back
CVE-2026-49336
Vulnerability in @microsoft/kiota-http-fetchlibrary (CVE-2026-49336)
Summary
vulnerability in @microsoft/kiota-http-fetchlibrary (CVE-2026-49336). Risk of unauthorized operations or information disclosure. Exploitable via `Authorization header`. Mitigation: upgrade to `1.0.0-preview.102` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-49336** has been found in @microsoft/kiota-http-fetchlibrary.
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 @microsoft/kiota-http-fetchlibrary to **1.0.0-preview.102** or later.
If unsure, ask your IT team or search "@microsoft/kiota-http-fetchlibrary CVE-2026-49336" on the vendor's site.
CVE-2026-49336 (@microsoft/kiota-http-fetchlibrary) — CWE-178 /
Attack surface: Authorization header / Cookie header / `RedirectHandler` / `Authorization`
Patched: `1.0.0-preview.102` — 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** (CWE-178) exists in @microsoft/kiota-http-fetchlibrary. Attackers reach the vulnerable code path via `Authorization header` without authentication.
📍 Affected scope
@microsoft/kiota-http-fetchlibrary — . Attack surface: Authorization header / Cookie header / `RedirectHandler` / `Authorization`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.0.0-preview.102**.
🛡️ 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 '@microsoft/kiota-http-fetchlibrary' .` 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 '@microsoft/kiota-http-fetchlibrary' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@microsoft/kiota-http-fetchlibrary` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade @microsoft/kiota-http-fetchlibrary to 1.0.0-preview.102ステージング環境で 1.0.0-preview.102 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@microsoft/kiota-http-fetchlibrary
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.0.0-preview.102"}]}]