CVE-2026-49509

MEDIUMPre-NVD 4.44.4—
EchelonGraph scoreHIGH confidence

Score 4.4 from GitHub Security Advisory published 2026-09-04. a secondary CVSS source baseline 4.4; sources differ by 0.0.

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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Out-of-bounds read vulnerability in Samsung Opensource rLottie allows Overread Buffers.

This issue affects rLottie: 25648aef19187b3f87f4d9420b8d761453ad4630.

CVSS v3
4.4
EG Score
4.4(high)
EG Risk
20(Track)
EG Risk 20/100SSVC: Track

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
Severity44% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

September 3, 2026

Last Modified

September 8, 2026

Advisory Details (1)

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

stb_image: don't deal with fractional ratios

Fix merged in Samsung/rlottie PR #604 on 2026-09-01 — awaiting tagged release

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

Vendor Advisories for CVE-2026-49509(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

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

  1. 2026-09-25 00:48 UTCEG score recompute
  2. 2026-09-25 00:48 UTCGHSA enrichment
  3. 2026-09-24 01:55 UTCEG score recompute
  4. 2026-09-24 01:55 UTCGHSA enrichment
  5. 2026-09-23 17:53 UTCEPSS rescore
  6. 2026-09-23 03:04 UTCEG score recompute
  7. 2026-09-23 03:04 UTCGHSA enrichment
  8. 2026-09-22 04:11 UTCEG score recompute
  9. 2026-09-22 04:11 UTCGHSA enrichment
  10. 2026-09-21 05:19 UTCEG score recompute
  11. 2026-09-21 05:19 UTCGHSA enrichment
  12. 2026-09-20 20:16 UTCEPSS rescore
  13. 2026-09-20 06:24 UTCEG score recompute
  14. 2026-09-20 06:24 UTCGHSA enrichment
  15. 2026-09-19 07:30 UTCEG score recompute
  16. 2026-09-19 07:30 UTCGHSA enrichment
  17. 2026-09-18 19:28 UTCEPSS rescore
  18. 2026-09-18 08:39 UTCEG score recompute
  19. 2026-09-18 08:39 UTCGHSA enrichment
  20. 2026-09-17 09:47 UTCEG score recompute
  21. 2026-09-17 09:47 UTCGHSA enrichment
  22. 2026-09-16 14:08 UTCEPSS rescore
  23. 2026-09-16 10:55 UTCEG score recompute
  24. 2026-09-16 10:55 UTCGHSA enrichment
  25. 2026-09-16 05:15 UTCEPSS rescore
Show 41 more
  1. 2026-09-15 12:04 UTCEG score recompute
  2. 2026-09-15 12:04 UTCGHSA enrichment
  3. 2026-09-14 13:11 UTCEG score recompute
  4. 2026-09-14 13:11 UTCGHSA enrichment
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-13 14:19 UTCGHSA enrichment
  7. 2026-09-12 15:27 UTCGHSA enrichment
  8. 2026-09-11 16:35 UTCEG score recompute
  9. 2026-09-11 16:35 UTCGHSA enrichment
  10. 2026-09-11 14:53 UTCEPSS rescore
  11. 2026-09-10 17:43 UTCEG score recompute
  12. 2026-09-10 17:43 UTCGHSA enrichment
  13. 2026-09-10 09:35 UTCEPSS rescore
  14. 2026-09-09 18:51 UTCEG score recompute
  15. 2026-09-09 18:51 UTCGHSA enrichment
  16. 2026-09-08 22:01 UTCEPSS rescore
  17. 2026-09-08 19:59 UTCGHSA enrichment
  18. 2026-09-07 21:28 UTCEG score recompute
  19. 2026-09-07 21:28 UTCGHSA enrichment
  20. 2026-09-07 16:01 UTCEPSS rescore
  21. 2026-09-06 22:36 UTCEG score recompute
  22. 2026-09-06 22:36 UTCGHSA enrichment
  23. 2026-09-06 21:44 UTCEG score recompute
  24. 2026-09-06 21:44 UTCGHSA enrichment
  25. 2026-09-06 18:10 UTCEG score recompute
  26. 2026-09-06 18:10 UTCGHSA enrichment
  27. 2026-09-06 13:47 UTCEPSS rescore
  28. 2026-09-05 19:18 UTCEG score recompute
  29. 2026-09-05 19:18 UTCGHSA enrichment
  30. 2026-09-04 20:26 UTCEG score recompute
  31. 2026-09-04 20:26 UTCGHSA enrichment
  32. 2026-09-04 20:05 UTCEG score recompute
  33. 2026-09-04 20:05 UTCGHSA enrichment
  34. 2026-09-04 06:30 UTCEG score recompute
  35. 2026-09-04 06:29 UTCGHSA enrichment
  36. 2026-09-04 06:01 UTCGHSA enrichment
  37. 2026-09-04 05:45 UTCEG score recompute
  38. 2026-09-04 05:45 UTCGHSA enrichment
  39. 2026-09-04 00:24 UTCEG score recompute
  40. 2026-09-03 23:20 UTCEG score recompute
  41. 2026-09-03 23:18 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-49509?
CVE-2026-49509 is a medium vulnerability published on September 3, 2026. Out-of-bounds read vulnerability in Samsung Opensource rLottie allows Overread Buffers. This issue affects rLottie: 25648aef19187b3f87f4d9420b8d761453ad4630.
When was CVE-2026-49509 disclosed?
CVE-2026-49509 was first published in the National Vulnerability Database on September 3, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49509 actively exploited?
CVE-2026-49509 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.5% of all scored CVEs.
What is the CVSS score of CVE-2026-49509?
CVE-2026-49509 has a CVSS v3 base score of 4.4 (NVD).
How do I remediate CVE-2026-49509?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49509, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-49509

Explore →

Is Your Infrastructure Affected by CVE-2026-49509?

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

Book a Demo →Browse All CVEs