Every CVE Search/ Get API key

OSV-2025-32

UNKNOWN READ in std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<ch

No scoreFix available

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=389754841

Crash type: UNKNOWN READ
Crash state:
std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<ch
Poco::Net::NTLMCredentials::parseChallengeMessage
Poco::Net::HTTPNTLMCredentials::createNTLMMessage

What each source reports

OSV No score

UNKNOWN READ in std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<ch

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=389754841

Crash type: UNKNOWN READ
Crash state:
std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<ch
Poco::Net::NTLMCredentials::parseChallengeMessage
Poco::Net::HTTPNTLMCredentials::createNTLMMessage
Record
OSV-2025-32
Updated
2026-11-02

Affected packages

Affected packages
PackageAffectedFixed
poco
OSS-Fuzz
Listed versions, plus commit ranges
poco-1.14.0-releasepoco-1.14.1-release
None known

History

History
RecordedChangedSources
first indexedOSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

In short

OSV-2025-32 is a vulnerability with no CVSS score yet in poco, published January 16, 2025. No source lists public exploit code. A source reports a fix.

References

MoveEnter Open