Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-11680: CWE-787 Out-of-bounds Write in warmcat libwebsockets

0
Medium
VulnerabilityCVE-2025-11680cvecve-2025-11680cwe-787
Published: Mon Oct 20 2025 (10/20/2025, 14:04:06 UTC)
Source: CVE Database V5
Vendor/Project: warmcat
Product: libwebsockets

Description

Out-of-bounds Write in unfilter_scanline in warmcat libwebsockets allows, when the LWS_WITH_UPNG flag is enabled during compilation and the HTML display stack is used, to write past a heap allocated buffer possibly causing a crash, when the user visits an attacker controlled website that contains a crafted PNG file with a big width value that causes an integer overflow which value is used for determining the size of a heap allocation.

AI-Powered Analysis

AILast updated: 10/20/2025, 14:16:23 UTC

Technical Analysis

CVE-2025-11680 is an out-of-bounds write vulnerability classified under CWE-787 found in the warmcat libwebsockets library, specifically in version 4.0. The flaw exists in the unfilter_scanline function when the library is compiled with the LWS_WITH_UPNG flag enabled and the HTML display stack is utilized. The vulnerability arises due to an integer overflow caused by a crafted PNG image with a large width value. This overflow affects the calculation of the heap allocation size, leading to a buffer overflow where data is written past the allocated heap buffer. The exploitation vector requires a victim to visit an attacker-controlled website hosting the malicious PNG file. The consequence of this vulnerability can be a denial of service (application crash) or potentially memory corruption that could be leveraged for further attacks, although no public exploits are known at this time. The CVSS 4.0 score is 5.9, reflecting a medium severity with network attack vector, high attack complexity, partial user interaction, and no privileges required. The vulnerability impacts applications embedding libwebsockets 4.0 with the specified configuration, commonly used for websocket communication and HTML display in embedded or IoT devices. The lack of patches or mitigations currently available increases the urgency for affected users to implement workarounds or monitor for updates.

Potential Impact

For European organizations, the impact of CVE-2025-11680 depends on their use of libwebsockets 4.0 with the LWS_WITH_UPNG flag enabled and the HTML display stack. Organizations running web-facing applications or embedded devices that process PNG images via libwebsockets are at risk of service disruption due to crashes. This can affect availability of critical services, especially in sectors relying on embedded systems such as industrial control, telecommunications, or IoT deployments prevalent in Europe. While no known exploits exist yet, the vulnerability could be weaponized to cause denial of service or potentially enable remote code execution if combined with other flaws. This poses a risk to confidentiality and integrity if exploited in complex attack chains. The medium severity score indicates moderate risk, but the network vector and no privilege requirement mean attackers can attempt exploitation remotely, increasing the threat surface. European organizations with critical infrastructure or sensitive data processed through affected systems should consider this vulnerability a priority for risk assessment and mitigation.

Mitigation Recommendations

1. Immediately audit all deployments of libwebsockets version 4.0 to identify usage of the LWS_WITH_UPNG flag and HTML display stack. 2. If possible, disable the LWS_WITH_UPNG flag or avoid using the HTML display stack until a patch is available. 3. Implement strict input validation and filtering on PNG files processed by libwebsockets to detect and block images with suspiciously large width values. 4. Employ network-level protections such as web application firewalls (WAFs) to detect and block malicious PNG payloads from untrusted sources. 5. Monitor vendor announcements and subscribe to security advisories for updates or patches addressing this vulnerability. 6. Consider isolating or sandboxing applications using libwebsockets to limit the impact of potential crashes or memory corruption. 7. Conduct penetration testing and fuzzing on affected systems to identify if the vulnerability can be exploited in the specific environment. 8. Prepare incident response plans to quickly address potential exploitation attempts. 9. Engage with vendors or open-source maintainers to accelerate patch development and deployment.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Nozomi
Date Reserved
2025-10-13T09:57:01.900Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68f6439468d8b0c0b432bc22

Added to database: 10/20/2025, 2:13:40 PM

Last enriched: 10/20/2025, 2:16:23 PM

Last updated: 10/20/2025, 4:45:02 PM

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats