CVE-2025-6375: A vulnerability was found in poco up to 1.14.1

Q: How do I fix CVE-2025-6375?

poco: upgrade to 1.14.2. Exact commands for each OS are on this page.

Q: Is CVE-2025-6375 being exploited?

CVE-2025-6375 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-6375 affect?

CVE-2025-6375 affects poco. Severity is low (CVSS 3.3). 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 a

Q: How urgent is CVE-2025-6375?

Priority 21/100. Public exploit reference

Routine

LOW 3.3UPGRADE

CVE-2025-6375 is a low-severity flaw (CVSS 3.3) affecting poco. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 6f2f85913c191ab9ddfb8fae

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	3.3 (Low)
Attack vector	Local
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 82%)
CISA exploited list	No
Weakness	CWE-404, CWE-476
Published	2025-06-21
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: pocoproject

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-06-21 01:15 UTCPublished CVE record published
2026-06-17 10:01 UTCUpdated Record last modified

pocoproject poco UPGRADE

Affected: < 1.14.2

Fixed in: 1.14.2

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy poco || rpm -q poco || poco --version

2. UPGRADE to 1.14.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade poco

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade poco

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-6375?

poco: upgrade to 1.14.2. Exact commands for each OS are on this page.

Is CVE-2025-6375 being exploited?

CVE-2025-6375 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-6375 affect?

CVE-2025-6375 affects poco. Severity is low (CVSS 3.3). 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 a

How urgent is CVE-2025-6375?

Priority 21/100. Public exploit reference

Related CVEs

CVE-2025-45766 HIGH 7.0 DOWNGRADE poco v1.14.1-release was discovered to contain weak encryption
CVE-2023-52389 CRITICAL 9.8 UPGRADE UTF32Encoding.cpp in POCO has a Poco::UTF32Encoding integer overflow and resultant stack buffer overflow becau

References

← Back to latest CVEs