CVE-2025-45766
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-08-06

Last updated on: 2025-08-17

Assigner: MITRE

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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-08-06
Last Modified
2025-08-17
Generated
2026-05-07
AI Q&A
2025-08-06
EPSS Evaluated
2026-05-05
NVD
CVE-2025-45766
EUVD
EUVD-2025-23873
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
pocoproject poco 1.14.1
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-327 The product uses a broken or risky cryptographic algorithm or protocol.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability in poco v1.14.1-release involves the use of weak encryption, which means that the cryptographic methods used to protect data are not strong enough to prevent unauthorized access or attacks.


How can this vulnerability impact me? :

The weak encryption can lead to unauthorized disclosure or modification of sensitive data, potentially causing data breaches, loss of data integrity, and disruption of services.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

Weak encryption may result in non-compliance with standards and regulations such as GDPR and HIPAA, which require strong protection of personal and sensitive data, potentially leading to legal and financial consequences.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart