CVE-2022-27938

Exp

stb_image.h (aka the stb image loader) 2.19, as used in libsixel and other products, has a reachable assertion in stbi__create_png_image_raw.

Published: 2022-03-26 Last update: 2026-04-24 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2022-27938 is rated Exploit Available (50/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.13%). Core evidence: 1 public exploit reference(s) are indexed (Exploit-DB). Mandatory action: Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

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

Public exploit references (Exploit-DB) for CVE-2022-27938

EDB-ID Source Kind Published Link
nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2022-27938

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 2025-04-23 0.26% 0.13% -0.13%
2 2025-04-07 0.15% 0.26% +0.11%
3 2025-04-06 0.15%

Full EPSS history (10 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-27938

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H 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:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
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:H)
Could take the service down hard or make it unusable for people who depend on it.
1.8 3.6 [email protected]
4.3 2.0 MEDIUM
AV:N/AC:M/Au:N/C:N/I:N/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:P)
Partial availability impact.
8.6 2.9 [email protected]

Weakness enumeration for CVE-2022-27938

OS Trackers for CVE-2022-27938

vendor priority summary link
debian unimportant CVE-2022-27938 unimportant priority: Debian including 1 source packages (libstb), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 5. https://security-tracker.debian.org/tracker/CVE-2022-27938
ubuntu medium CVE-2022-27938 medium priority: Ubuntu including 1 source packages (libstb), 13 status rows across 13 suites (focal, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): ignored 8, needs-triage 5. https://ubuntu.com/security/CVE-2022-27938

Affected software / configurations for CVE-2022-27938

Vendor Product Version Raw CPE
libsixel libsixel < 1.10.4 cpe:2.3:a:libsixel:libsixel:*:*:*:*:*:*:*:*
saitoha libsixel < 1.8.7 cpe:2.3:a:saitoha:libsixel:*:*:*:*:*:*:*:*

References for CVE-2022-27938

URL Tags
https://github.com/saitoha/libsixel/issues/163 Exploit Issue Tracking Patch Third Party Advisory
cvelogic Threat Intelligence