Vulnerability in elysia (CVE-2026-56669)
Summary
Vulnerability in elysia (CVE-2026-56669). Risk of unauthorized operations or information disclosure. Exploitable via getAll. Mitigation: upgrade to 1.4.29 or later.
Original description
The description as published by the source.
Elysia is a Typescript framework for request validation, type inference, OpenAPI documentation, and client-server communication. Prior to 1.4.29, Elysia uses getAll in form data normalization for multipart/form-data endpoints, causing the amount of work to grow quadratically with the number of unique key-value pairs and allowing CPU exhaustion. This issue is fixed in version 1.4.29.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-56669 has been found in elysia.
Attackers can target a specific entry point like getAll over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade elysia to 1.4.29 or later.
If unsure, ask your IT team or search "elysia CVE-2026-56669" on the vendor's site.
CVE-2026-56669 (elysia) — CWE-407 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: getAll
Patched: 1.4.29 — apply immediately
Workaround: no 100% confirm workaround beside updating the patch
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.
A vulnerability (CWE-407) exists in elysia. Attackers reach the vulnerable code path via getAll without authentication.
Check the vendor advisory for the affected versions of elysia. Attack surface: getAll.
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.
Update to 1.4.29.
Workaround: no 100% confirm workaround beside updating the patch
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'elysia' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'elysia' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
elysiaを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
no 100% confirm workaround beside updating the patchパッチが適用されるまでの応急処置として、no 100% confirm workaround beside updating the patch を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade elysia to 1.4.29ステージング環境で 1.4.29 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- patch github.com
- web gist.github.com
- web github.com
- web github.com