CVE-2026-19517

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

Score 6.5 from GitHub Security Advisory published 2026-08-11. A secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.5Exploit: None knownExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

Improper Validation of Specified Quantity in Input and Allocation of Resources Without Limits or Throttling vulnerability in Samsung Open Source rlottie allows Excessive Allocation.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/100CISA SSVC

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 computed
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.
EPSS PROB
0.4%
EPSS %ILE
26th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 11, 2026

Last Modified

September 23, 2026

Advisory Details (1)

Auto-updated Aug 11, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr.
github_pr

Safety limits to precomp, repeater, and polystar handling

Fix merged in Samsung/rlottie PR #596 on 2026-07-22 — awaiting tagged release

https://github.com/Samsung/rlottie/pull/596

Vendor Advisories for CVE-2026-19517(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
rlottie0.1+dfsg-4 ... 0.1+dfsg-5 (7 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
rlottie0.1+dfsg-4.2, 0.1+dfsg-4.2+deb13u1, 0.1+dfsg-4.2+deb13u2, 0.1+dfsg-4.3, 0.1+dfsg-5
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
rlottie0.1+dfsg-4.2, 0.1+dfsg-4.3, 0.1+dfsg-5
  • every version on: no fix on record
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 68× 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.

Showing the most recent 100 of 143 total refreshes for this CVE.

  1. 2026-10-04 23:21 UTCEPSS rescore
  2. 2026-10-04 22:48 UTCGHSA enrichment
  3. 2026-10-03 21:39 UTCEG score recompute
  4. 2026-10-03 21:39 UTCGHSA enrichment
  5. 2026-10-02 09:14 UTCEG score recompute
  6. 2026-10-02 09:14 UTCGHSA enrichment
  7. 2026-10-01 19:49 UTCEPSS rescore
  8. 2026-09-30 22:22 UTCEG score recompute
  9. 2026-09-30 22:22 UTCGHSA enrichment
  10. 2026-09-30 15:03 UTCEPSS rescore
  11. 2026-09-29 15:20 UTCEPSS rescore
  12. 2026-09-29 07:20 UTCEG score recompute
  13. 2026-09-29 07:20 UTCGHSA enrichment
  14. 2026-09-28 13:51 UTCEPSS rescore
  15. 2026-09-28 09:09 UTCEG score recompute
  16. 2026-09-28 09:09 UTCGHSA enrichment
  17. 2026-09-27 13:47 UTCEPSS rescore
  18. 2026-09-27 11:04 UTCEG score recompute
  19. 2026-09-27 11:04 UTCGHSA enrichment
  20. 2026-09-26 15:58 UTCEPSS rescore
  21. 2026-09-25 03:58 UTCEG score recompute
  22. 2026-09-25 03:58 UTCGHSA enrichment
  23. 2026-09-23 16:00 UTCEG score recompute
  24. 2026-09-23 16:00 UTCGHSA enrichment
  25. 2026-09-22 21:15 UTCEG score recompute
Show 75 more
  1. 2026-09-22 21:15 UTCGHSA enrichment
  2. 2026-09-21 21:21 UTCEG score recompute
  3. 2026-09-21 21:21 UTCGHSA enrichment
  4. 2026-09-20 19:43 UTCGHSA enrichment
  5. 2026-09-19 21:19 UTCEG score recompute
  6. 2026-09-19 21:19 UTCGHSA enrichment
  7. 2026-09-18 22:52 UTCEG score recompute
  8. 2026-09-18 22:52 UTCGHSA enrichment
  9. 2026-09-18 19:27 UTCEPSS rescore
  10. 2026-09-18 00:47 UTCEG score recompute
  11. 2026-09-18 00:47 UTCGHSA enrichment
  12. 2026-09-17 00:39 UTCEG score recompute
  13. 2026-09-17 00:39 UTCGHSA enrichment
  14. 2026-09-16 14:07 UTCEPSS rescore
  15. 2026-09-16 05:14 UTCEPSS rescore
  16. 2026-09-16 02:20 UTCEG score recompute
  17. 2026-09-16 02:20 UTCGHSA enrichment
  18. 2026-09-14 22:48 UTCGHSA enrichment
  19. 2026-09-13 21:23 UTCEG score recompute
  20. 2026-09-13 21:23 UTCGHSA enrichment
  21. 2026-09-13 16:46 UTCEPSS rescore
  22. 2026-09-12 23:17 UTCEG score recompute
  23. 2026-09-12 23:17 UTCGHSA enrichment
  24. 2026-09-12 15:00 UTCEPSS rescore
  25. 2026-09-12 00:17 UTCEG score recompute
  26. 2026-09-12 00:17 UTCGHSA enrichment
  27. 2026-09-11 14:52 UTCEPSS rescore
  28. 2026-09-11 09:36 UTCEPSS rescore
  29. 2026-09-11 02:02 UTCEG score recompute
  30. 2026-09-11 02:02 UTCGHSA enrichment
  31. 2026-09-10 09:34 UTCEPSS rescore
  32. 2026-09-10 03:57 UTCGHSA enrichment
  33. 2026-09-09 05:47 UTCEG score recompute
  34. 2026-09-09 05:47 UTCGHSA enrichment
  35. 2026-09-08 22:00 UTCEPSS rescore
  36. 2026-09-07 20:36 UTCEG score recompute
  37. 2026-09-07 20:35 UTCGHSA enrichment
  38. 2026-09-07 16:01 UTCEPSS rescore
  39. 2026-09-06 22:30 UTCEG score recompute
  40. 2026-09-06 22:30 UTCGHSA enrichment
  41. 2026-09-06 13:47 UTCEPSS rescore
  42. 2026-09-06 00:24 UTCEG score recompute
  43. 2026-09-06 00:24 UTCGHSA enrichment
  44. 2026-09-05 02:11 UTCEG score recompute
  45. 2026-09-05 02:11 UTCGHSA enrichment
  46. 2026-09-04 05:06 UTCEPSS rescore
  47. 2026-09-04 04:05 UTCGHSA enrichment
  48. 2026-09-03 05:57 UTCEG score recompute
  49. 2026-09-03 05:57 UTCGHSA enrichment
  50. 2026-09-02 14:11 UTCEPSS rescore
  51. 2026-09-02 06:23 UTCEG score recompute
  52. 2026-09-02 06:23 UTCGHSA enrichment
  53. 2026-09-01 13:53 UTCEPSS rescore
  54. 2026-09-01 06:44 UTCEG score recompute
  55. 2026-09-01 06:43 UTCGHSA enrichment
  56. 2026-09-01 04:39 UTCEPSS rescore
  57. 2026-08-31 06:02 UTCEG score recompute
  58. 2026-08-31 06:02 UTCGHSA enrichment
  59. 2026-08-30 19:17 UTCEPSS rescore
  60. 2026-08-30 07:56 UTCEG score recompute
  61. 2026-08-30 07:56 UTCGHSA enrichment
  62. 2026-08-30 01:22 UTCEPSS rescore
  63. 2026-08-29 09:48 UTCEG score recompute
  64. 2026-08-29 09:48 UTCGHSA enrichment
  65. 2026-08-28 21:41 UTCEPSS rescore
  66. 2026-08-27 20:42 UTCEG score recompute
  67. 2026-08-27 20:42 UTCGHSA enrichment
  68. 2026-08-27 14:25 UTCEPSS rescore
  69. 2026-08-26 22:36 UTCEG score recompute
  70. 2026-08-26 22:36 UTCGHSA enrichment
  71. 2026-08-26 14:46 UTCEPSS rescore
  72. 2026-08-26 00:30 UTCEG score recompute
  73. 2026-08-26 00:30 UTCGHSA enrichment
  74. 2026-08-25 13:48 UTCEPSS rescore
  75. 2026-08-25 02:17 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-19517?
CVE-2026-19517 is a medium vulnerability published on August 11, 2026. Improper Validation of Specified Quantity in Input and Allocation of Resources Without Limits or Throttling vulnerability in Samsung Open Source rlottie allows Excessive Allocation.
When was CVE-2026-19517 disclosed?
CVE-2026-19517 was first published on August 11, 2026, with the most recent update on September 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-19517 actively exploited?
CVE-2026-19517 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (26th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-19517?
CVE-2026-19517 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-19517?
An upstream fix for CVE-2026-19517 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-19517 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-19517

Explore →

Is Your Infrastructure Affected by CVE-2026-19517?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs