← Back
CVE-2026-25577
Vulnerability in emmett-core (CVE-2026-25577)
Summary
vulnerability in emmett-core (CVE-2026-25577). Risk of unauthorized operations or information disclosure. Exploitable via `Cookie header`. Mitigation: upgrade to `1.3.11` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-25577** has been found in emmett-core.
Attackers can target a specific entry point like `Cookie header` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade emmett-core to **1.3.11** or later.
If unsure, ask your IT team or search "emmett-core CVE-2026-25577" on the vendor's site.
CVE-2026-25577 (emmett-core) — CWE-248 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: Cookie header / `cookies` / `emmett_core.http.wrappers.Request` / `CookieError`
Patched: `1.3.11` — 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-248) exists in emmett-core. Attackers reach the vulnerable code path via `Cookie header` without authentication.
📍 Affected scope
emmett-core — . Attack surface: Cookie header / `cookies` / `emmett_core.http.wrappers.Request` / `CookieError`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.3.11**.
🛡️ 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 'emmett-core' .` 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 'emmett-core' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `emmett-core` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade emmett-core to 1.3.11ステージング環境で 1.3.11 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
emmett-core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.3.11"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-25577
- advisory https://github.com/advisories/GHSA-x6cr-mq53-cc76
- package https://github.com/emmett-framework/core
- package https://pypi.org/project/emmett-core
- web https://github.com/emmett-framework/core/security/advisories/GHSA-x6cr-mq53-cc76
- web https://github.com/emmett-framework/core/commit/9557ea23a27cbadf7774d8bca6bbe4b54fa8a3ec
- web https://github.com/emmett-framework/core/commit/c126757133e118119a280b58f3bb345b1c9a8a2a