CVE-2025-50422

Cairo through 1.18.4, as used in Poppler through 25.08.0, has an "unscaled->face == NULL" assertion failure for _cairo_ft_unscaled_font_fini in cairo-ft-font.c.

Published: 2025-08-04 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-50422 is rated Low Risk (15.4/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.21%). Low composite risk—no urgent action required; patch on your normal maintenance cycle and revisit priority if CVSS or EPSS increases.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-50422

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.10% 0.21% +0.11%
2 2026-05-31 0.03% 0.10% +0.07%
3 2026-04-23 — 0.03% —

Full EPSS history (5 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-50422

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
2.9 3.1 LOW
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 1.4 1.4 [email protected]

Weakness enumeration for CVE-2025-50422

OS Trackers for CVE-2025-50422

vendor priority summary link
alpine — CVE-2025-50422: 1 source package rows (cairo); 27 state rows across 6 repos (3.19-main, 3.20-main, 3.21-main, 3.22-main, 3.23-main, edge-main); fixed 0, open 27. https://security.alpinelinux.org/vuln/CVE-2025-50422
debian not yet assigned CVE-2025-50422 not yet assigned priority: Debian including 1 source packages (cairo), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 5. https://security-tracker.debian.org/tracker/CVE-2025-50422
redhat low — https://access.redhat.com/security/cve/CVE-2025-50422
suse low CVE-2025-50422 severity low: SUSE including 264 source package names (0.6.18-12.30:libcairo2-1.18.4-150600.3.3.1, 0.9.1-3.40:libcairo2-1.18.4-150600.3.3.1, …), 472 product×package rows across 121 product lines (Container containers/open-webui, Container containers/vllm-openai, … (121 product lines)): Fixed 241, Known Affected 231. https://www.suse.com/security/cve/CVE-2025-50422/
ubuntu low CVE-2025-50422 low priority: Ubuntu including 1 source packages (cairo), 8 status rows across 8 suites (bionic, focal, jammy, noble, plucky, questing, upstream, xenial): needs-triage 7, ignored 1. https://ubuntu.com/security/CVE-2025-50422

Affected software / configurations for CVE-2025-50422

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-50422

cvelogic Threat Intelligence