OSV-2025-275 UNKNOWN READ in void std::__1::vector<unsigned char, std::__1::allocator<unsigned char>>::__cons

Not scored Published

An unknown read vulnerability in the Poco library's NTLM credential parsing can cause a crash, potentially leading to denial of service.

Exploited in the wild
Not known
Login needed
Not stated
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is OSV-2025-275?

OSV-2025-275 is a memory corruption vulnerability in poco, published on 14 Apr 2025. It can be exploited over the network, with no action from the victim.

Official description

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

Crash type: UNKNOWN READ
Crash state:
void std::__1::vector&lt;unsigned char, std::__1::allocator&lt;unsigned char&gt;&gt;::__cons
Poco::Net::NTLMCredentials::parseChallengeMessage
Poco::Net::HTTPNTLMCredentials::createNTLMMessage

Which versions are affected by OSV-2025-275?

1 open source package ship an affected version, including poco.

PackageAffectedFixed in
poco OSS-FuzzAll versionsNone

How do I fix OSV-2025-275?

No fix has been published for OSV-2025-275 yet. Limit exposure of the affected software until one is available.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is OSV-2025-275 being exploited?

There is no known exploitation of OSV-2025-275 in the wild and no public exploit code.

Sources

Is OSV-2025-275 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free