Skip to content
Fencer Intel
critical 9.8

CVE-2025-53075 json

Improper Input Validation vulnerability in Samsung Open Source rLottie allows Path Traversal.This issue affects rLottie: V0.2.

published last yr. modified 4mo ago also EUVD-2025-19504

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 20%
public exploits
0
none known

Summary

Improper Input Validation vulnerability in Samsung Open Source rLottie allows Path Traversal.This issue affects rLottie: V0.2.

Patch / fix

  • rlottie Debian 12 0.1+dfsg-4+deb12u1
  • rlottie Debian 13 0.1+dfsg-4.2+deb13u1
  • rlottie Debian 14 0.1+dfsg-4.3

debian advisories DEBIAN-CVE-2025-53075

  • rlottie Ubuntu 22.04 LTS 0.1+dfsg-2ubuntu0.2
  • rlottie Ubuntu 24.04 LTS 0.1+dfsg-4ubuntu1.1
  • rlottie Ubuntu 25.10 0.1+dfsg-4.2ubuntu0.1
  • rlottie Ubuntu Pro 20.04 LTS 0~git20200305.a717479+dfsg-1ubuntu0.1~esm2

ubuntu advisories UBUNTU-CVE-2025-53075

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2025-53075 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.28% chance of exploitation in the next 30 days, higher than 20% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 4.0 4.6 CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
CNA 4.0 4.6 CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

  • Samsung Open Source rLottie

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.