Skip to main content
VulnerabilityPublished Updated

CVE-2025-45766: poco · Weak Cryptography

Source CVE Database V5

0

Not known to be exploited · CVSS 7.0 High.

Data as of 26 Oct 2026, 15:59 UTC

CVSS 3.1 base score
7.0High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

European organizations should conduct a thorough audit of all software components using the poco library, specifically version 1.14.1-release, to identify where weak encryption might be configured or enforced. Since the vulnerability centers on key length and cryptographic strength set by the application, developers must ensure that strong, industry-standard cryptographic parameters are explicitly defined and enforced in their implementations. This includes using sufficiently long keys (e.g., AES-256), secure cipher modes, and up-to-date cryptographic algorithms. Organizations should also monitor vendor communications and security advisories for official patches or updates to the poco library that address this issue. In the interim, applying compensating controls such as network-level protections (firewalls, intrusion detection systems) to limit exposure of vulnerable services can reduce risk. Additionally, implementing robust logging and anomaly detection can help identify exploitation attempts. Security teams should also review their incident response plans to prepare for potential availability-impacting attacks. Finally, engaging with software vendors or open-source maintainers to clarify the dispute and encourage resolution will help ensure long-term security.

Description

poco v1.14.1-release was discovered to contain weak encryption. NOTE: this issue has been disputed on the basis that key lengths are expected to be set by an application, not by this library. This dispute is subject to review under CNA rules 4.1.4, 4.1.14, and other rules; the dispute tagging is not meant to recommend an outcome for this CVE Record.

References

Community reviews

Loading reviews…