A vulnerability was identified in evanchiu serverless-todo 1.0.3/2.0.0. Impacted is the function saveTodos of the file src/index.js of the component API Todo Endpoint. Such manipulation of the argument event.body leads to resource consumption. The attack can be executed remotely. The exploit is publicly available and might be used. The project was informed of the problem early through an issue report but has not responded yet.
CVE-2026-90582
Score 5.3 from GitHub Security Advisory published 2026-09-13. a secondary CVSS source baseline 5.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(high)
- EG Risk
- 55(Attend)EG Risk 55/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity53% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 35%
- KEV
- Not listed
Published
September 13, 2026
Last Modified
September 15, 2026
Advisory Details (2)
Auto-updated Sep 13, 2026GitHub - evanchiu/serverless-todo: React TodoMVC with a Serverless backend · GitHub
https://github.com/evanchiu/serverless-todo/Unauthenticated resource consumption via unbounded `/api/todos` JSON body · Issue #10 · evanchiu/serverless-todo · GitHub
https://github.com/evanchiu/serverless-todo/issues/10Vendor Advisories for CVE-2026-90582(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 25× in last 7d / 25× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-19 16:12 UTCEG score recompute
- 2026-09-19 16:12 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 16:10 UTCEG score recompute
- 2026-09-18 16:10 UTCGHSA enrichment
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-17 15:36 UTCGHSA enrichment
- 2026-09-16 15:34 UTCEG score recompute
- 2026-09-16 15:34 UTCGHSA enrichment
- 2026-09-16 14:09 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 15:32 UTCEG score recompute
- 2026-09-15 15:32 UTCGHSA enrichment
- 2026-09-15 15:31 UTCNVD updateCVSS v4 → 5.5
- 2026-09-15 14:18 UTCEG score recompute
- 2026-09-15 14:18 UTCGHSA enrichment
- 2026-09-15 14:18 UTCMITRE cvelistV5CVSS v4 → 6.9
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-14 21:06 UTCGHSA enrichment
- 2026-09-14 20:27 UTCEG score recompute
- 2026-09-14 20:27 UTCGHSA enrichment
- 2026-09-13 20:25 UTCEG score recompute
- 2026-09-13 20:24 UTCNVD updateCVSS v4 → 5.5
- 2026-09-13 19:54 UTCEG score recompute
- 2026-09-13 19:54 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-90582?
When was CVE-2026-90582 disclosed?
Is CVE-2026-90582 actively exploited?
What is the CVSS score of CVE-2026-90582?
How do I remediate CVE-2026-90582?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-90582
Is Your Infrastructure Affected by CVE-2026-90582?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.