CVE-2022-41409

Exp

Integer overflow vulnerability in pcre2test before 10.41 allows attackers to cause a denial of service or other unspecified impacts via negative input.

Published: 2023-07-18 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-41409 is rated Exploit Available (50.5/100): CVSS High severity, with low exploitation likelihood (EPSS 0.05%). 1 public exploit reference(s) are indexed (Exploit-DB). 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-41409

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

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

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-01 0.05% 0.05% -0.00%
2 2026-05-22 0.05% 0.05% +0.00%
3 2026-02-25 — 0.05% —

Full EPSS history (11 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
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: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:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2022-41409

OS Trackers for CVE-2022-41409

vendor priority summary link
alpine high CVE-2022-41409: 1 source package rows (pcre2); 12 state rows across 7 repos (3.17-main, 3.18-main, 3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 7, open 5. https://security.alpinelinux.org/vuln/CVE-2022-41409
debian unimportant CVE-2022-41409 unimportant priority: Debian including 1 source packages (pcre2), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1. https://security-tracker.debian.org/tracker/CVE-2022-41409
redhat low — https://access.redhat.com/security/cve/CVE-2022-41409
suse medium CVE-2022-41409 severity moderate: SUSE including 299 source package names (1.11.9.0.4.7.1:libpcre2-8-0-10.31-150000.3.15.1, 1.20-openssl:libpcre2-8-0-10.39-150400.4.9.1, …), 800 product×package rows across 237 product lines (Container bci/golang, Container bci/node, … (237 product lines)): Fixed 375, Known Not Affected 255, Known Affected 170. https://www.suse.com/security/cve/CVE-2022-41409/
ubuntu low CVE-2022-41409 low priority: Ubuntu including 1 source packages (pcre2), 13 status rows across 13 suites (bionic, focal, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): ignored 4, needed 4, not-affected 4, needs-triage 1. https://ubuntu.com/security/CVE-2022-41409

Affected software / configurations for CVE-2022-41409

Vendor Product Version Raw CPE
pcre pcre2 < 10.41 cpe:2.3:a:pcre:pcre2:*:*:*:*:*:*:*:*

References for CVE-2022-41409

cvelogic Threat Intelligence