CVE-2025-6375 json
poco MultipartReader.cpp MultipartInputStream null pointer dereference
published last yr. modified 4mo ago also EUVD-2025-18796
- cvss
- 3.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 17%
- public exploits
- 0
- none known
Summary
A vulnerability was found in poco up to 1.14.1. It has been rated as problematic. Affected by this issue is the function MultipartInputStream of the file Net/src/MultipartReader.cpp. The manipulation leads to null pointer dereference. The attack needs to be approached locally. The exploit has been disclosed to the public and may be used. Upgrading to version 1.14.2 is able to address this issue. The patch is identified as 6f2f85913c191ab9ddfb8fae781f5d66afccf3bf. It is recommended to upgrade the affected component.
Patch / fix
- n/a poco 1.14.2
- poco Debian 13 1.13.0-6+deb13u1
- poco Debian 14 1.14.2-2
debian advisories DEBIAN-CVE-2025-6375
- poco openSUSE Tumbleweed 1.14.2-1.1
opensuse advisories openSUSE-SU-2025:15322-1
Is CVE-2025-6375 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 FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-6375 updated cvss 3.3
poco: Poco MultipartInputStream Null Pointer Dereference
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.26% chance of exploitation in the next 30 days, higher than 17% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/pocoproject/poco/commit/6f2f85913c191ab9ddfb8fae781f5d66afccf3bf referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/pocoproject/poco/releases/tag/poco-1.14.2-release referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/pocoproject/poco/issues/4915 referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/user-attachments/files/19524599/poco_crash.txt referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 4.8 | CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P |
| CNA | 3.1 | 3.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L/E:P/RL:O/RC:C |
| CNA | 3.0 | 3.3 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L/E:P/RL:O/RC:C |
| CNA | 2.0 | 1.7 | AV:L/AC:L/Au:S/C:N/I:N/A:P/E:POC/RL:OF/RC:C |
| CNA | 4.0 | 1.9 | CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P/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 |
| CNA | 3.1 | 3.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L |
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| CNA | 2.0 | 1.7 | AV:L/AC:L/Au:S/C:N/I:N/A:P |
Affected products
- n/a poco
Classification
References
-
github.com
/pocoproject/poco/commit/6f2f85913c191ab9ddfb8fae781f5d66afccf3bf
exploit, patch
-
github.com
/pocoproject/poco/releases/tag/poco-1.14.2-release
exploit, patch, release-notes
-
github.com
/pocoproject/poco/issues/4915
exploit, issue-tracking, patch
-
github.com
/user-attachments/files/19524599/poco_crash.txt
exploit
-
vuldb.com
/?id.313370
vdb-entry, technical-description, third-party-advisory
-
vuldb.com
/?ctiid.313370
signature, permissions-required, vdb-entry
-
vuldb.com
/?submit.597446
third-party-advisory, vdb-entry
Sources
- CVE List CVE-2025-6375
- NVD CVE-2025-6375
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.