CVE-2026-47319
Telemetry drift only. No threshold crossed and no authority ruling changed.
CVE record, CISA KEV and EPSS as of 2026-10-18.
CVEs like this one computed, by meaning
What to do now held facts and links
- The CVE record names a fix, but not as a version that can be installed. What it holds is a source commit, a placeholder, or a version the record itself lists as affected. The CNA's first reference is the place to look: github.com
- Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
- Check your version against the ranges this record publishes.
What it is stated by the CNA
Memory allocation with excessive size value vulnerability in Samsung Open Source rlottie allows Excessive Allocation. This issue affects rlottie: before 0b4e308fa88c72cbb60cc8a2c1d2c2ad89b101dd.
- weakness
- CWE-789 Memory allocation with excessive size value
- affected
- Samsung Open Source rlottie
- versions
- No affected-version range in held sources.
- fixed in
- The CVE record names a fix, but not as a version that can be installed. What it holds is a source commit, a placeholder, or a version the record itself lists as affected.
- severity
- 6.1 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H
- assigned by
- samsung.tv_appliance
- published
- 2026-06-04
check us github.com
Exploit code held, dated
- exploit code
- None held in the PoC-in-GitHub feed. A public repository changes this brief.
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 4 Jun 2026 | 0.00013 | |
| 10 Jun 2026 | 0.00014 | |
| 15 Jun 2026 | 0.00103 | scoring model v2026.06.15 |
| 28 Sep 2026 | 0.00148 |
4 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.
Outside the record researched, cited
This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.
What would change this brief held, dated
- CISA KEV
- Not listed in the catalogue we hold. A listing changes this brief.
- exploit probability
- 0.00 on 2026-09-28 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
- fix
- The record names a fix that is not an installable version. A version from the CNA or OSV changes this brief.
How to check this
Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:
SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2026-47319', '2026-10-29T23:59:59.999999Z', now());