Linux
rlottie security updates
Patch Radar has 37 security fixes for rlottie, closing 12 CVEs. The newest security fix is DEBIAN-CVE-2026-19587 (0.1+dfsg-4), released August 12, 2026.
Latest version
n/a
Release date not known
Security fixes
37
On record in Patch Radar
CVEs
12
Closed by those fixes
Exploited
0
Vendor report or CISA KEV
Security fixes, newest first
| Priority | Fix | Release | Fixed in | CVEs | Exploited | Released |
|---|---|---|---|---|---|---|
| Routine | DEBIAN-CVE-2026-19587 | Debian 12.15 (bookworm) | 0.1+dfsg-4 | 1 | Aug 12, 2026 | |
| Routine | DEBIAN-CVE-2026-19587 | Debian 13.5 (trixie) | 0.1+dfsg-4 | 1 | Aug 12, 2026 | |
| Routine | DEBIAN-CVE-2026-19587 | Debian 14 | 0.1+dfsg-4 | 1 | Aug 12, 2026 | |
| Routine | DEBIAN-CVE-2026-18772 | Debian 12.15 (bookworm) | 0.1+dfsg-4 | 1 | Aug 4, 2026 | |
| Routine | DEBIAN-CVE-2026-18772 | Debian 13.5 (trixie) | 0.1+dfsg-4 | 1 | Aug 4, 2026 | |
| Routine | DEBIAN-CVE-2026-18772 | Debian 14 | 0.1+dfsg-4 | 1 | Aug 4, 2026 | |
| Routine | DEBIAN-CVE-2026-47320 | Debian 14 | 0.1+dfsg-5 | 1 | Jun 24, 2026 | |
| Routine | DEBIAN-CVE-2026-47320 | Debian 12.15 (bookworm) | 0.1+dfsg-4+deb12u2 | 1 | Jun 24, 2026 | |
| Routine | DEBIAN-CVE-2026-47320 | Debian 13.5 (trixie) | 0.1+dfsg-4.2+deb13u2 | 1 | Jun 24, 2026 | |
| Routine | DEBIAN-CVE-2026-10305 | Debian 14 | 0.1+dfsg-5 | 1 | Jun 24, 2026 | |
| Routine | DEBIAN-CVE-2026-10305 | Debian 12.15 (bookworm) | 0.1+dfsg-4+deb12u2 | 1 | Jun 24, 2026 | |
| Routine | DEBIAN-CVE-2026-10305 | Debian 13.5 (trixie) | 0.1+dfsg-4.2+deb13u2 | 1 | Jun 24, 2026 | |
| Routine | DEBIAN-CVE-2026-47319 | Debian 14 | 0.1+dfsg-5 | 1 | Jun 24, 2026 | |
| Routine | DEBIAN-CVE-2026-47319 | Debian 12.15 (bookworm) | 0.1+dfsg-4+deb12u2 | 1 | Jun 24, 2026 | |
| Routine | DEBIAN-CVE-2026-47319 | Debian 13.5 (trixie) | 0.1+dfsg-4.2+deb13u2 | 1 | Jun 24, 2026 | |
| Routine | DEBIAN-CVE-2026-8916 | Debian 12.15 (bookworm) | 0.1+dfsg-3 | 1 | Jun 4, 2026 | |
| Routine | DEBIAN-CVE-2026-8916 | Debian 13.5 (trixie) | 0.1+dfsg-3 | 1 | Jun 4, 2026 | |
| Routine | DEBIAN-CVE-2026-8916 | Debian 14 | 0.1+dfsg-3 | 1 | Jun 4, 2026 | |
| Routine | DEBIAN-CVE-2026-47318 | Debian 12.15 (bookworm) | 0.1+dfsg-3 | 1 | Jun 4, 2026 | |
| Routine | DEBIAN-CVE-2026-47318 | Debian 13.5 (trixie) | 0.1+dfsg-3 | 1 | Jun 4, 2026 | |
| Routine | DEBIAN-CVE-2026-47318 | Debian 14 | 0.1+dfsg-3 | 1 | Jun 4, 2026 | |
| Routine | DEBIAN-CVE-2026-49510 | Debian 12.15 (bookworm) | 0.1+dfsg-1 | 1 | Jun 4, 2026 | |
| Routine | DEBIAN-CVE-2026-49510 | Debian 13.5 (trixie) | 0.1+dfsg-1 | 1 | Jun 4, 2026 | |
| Routine | DEBIAN-CVE-2026-49510 | Debian 14 | 0.1+dfsg-1 | 1 | Jun 4, 2026 | |
| Routine | DEBIAN-CVE-2026-47306 | Debian 12.15 (bookworm) | 0.1+dfsg-3 | 1 | Jun 4, 2026 | |
| Routine | DEBIAN-CVE-2026-47306 | Debian 13.5 (trixie) | 0.1+dfsg-3 | 1 | Jun 4, 2026 | |
| Routine | DEBIAN-CVE-2026-47306 | Debian 14 | 0.1+dfsg-3 | 1 | Jun 4, 2026 | |
| Urgent | DLA-4474-1 | Debian 11.6 (bullseye) | 0.1+dfsg-2+deb11u1 | 1 | Feb 9, 2026 | |
| Urgent | DEBIAN-CVE-2025-53074 | Debian 14 | 0.1+dfsg-4.3 | 1 | Jun 30, 2025 | |
| Urgent | DEBIAN-CVE-2025-53074 | Debian 12.15 (bookworm) | 0.1+dfsg-4+deb12u1 | 1 | Jun 30, 2025 | |
| Urgent | DEBIAN-CVE-2025-53074 | Debian 13.5 (trixie) | 0.1+dfsg-4.2+deb13u1 | 1 | Jun 30, 2025 | |
| Urgent | DEBIAN-CVE-2025-53075 | Debian 12.15 (bookworm) | 0.1+dfsg-4+deb12u1 | 1 | Jun 30, 2025 | |
| Urgent | DEBIAN-CVE-2025-53075 | Debian 13.5 (trixie) | 0.1+dfsg-4.2+deb13u1 | 1 | Jun 30, 2025 | |
| Urgent | DEBIAN-CVE-2025-53075 | Debian 14 | 0.1+dfsg-4.3 | 1 | Jun 30, 2025 | |
| Urgent | DEBIAN-CVE-2025-0634 | Debian 12.15 (bookworm) | 0.1+dfsg-4+deb12u1 | 1 | Jun 30, 2025 | |
| Urgent | DEBIAN-CVE-2025-0634 | Debian 13.5 (trixie) | 0.1+dfsg-4.2+deb13u1 | 1 | Jun 30, 2025 | |
| Urgent | DEBIAN-CVE-2025-0634 | Debian 14 | 0.1+dfsg-4.3 | 1 | Jun 30, 2025 |
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.