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-70314: n/a

0
Critical
VulnerabilityCVE-2025-70314cvecve-2025-70314
Published: Thu Feb 12 2026 (02/12/2026, 00:00:00 UTC)
Source: CVE Database V5

Description

webfsd 1.21 is vulnerable to a Buffer Overflow via a crafted request. This is due to the filename variable

AI-Powered Analysis

AILast updated: 02/12/2026, 20:04:30 UTC

Technical Analysis

CVE-2025-70314 identifies a buffer overflow vulnerability in webfsd version 1.21, a lightweight web server software. The flaw arises from improper handling of the filename variable when processing crafted HTTP requests. Specifically, the buffer allocated for the filename is insufficiently checked, allowing an attacker to overflow the buffer by sending a specially crafted request containing an overly long or malformed filename. This overflow can corrupt memory, potentially enabling arbitrary code execution or causing the web server to crash, resulting in denial of service. The vulnerability does not require authentication, and exploitation can be performed remotely by sending malicious HTTP requests to the affected server. Although no known exploits are currently reported in the wild, the nature of buffer overflows and the lack of input validation make this a critical risk if weaponized. The vulnerability affects version 1.21 of webfsd, which is commonly deployed in embedded systems, legacy devices, or specialized environments where lightweight web servers are preferred. The absence of a CVSS score indicates that the vulnerability has not yet been fully assessed, but the technical characteristics suggest a high severity due to the potential for remote code execution and service disruption. No official patches or mitigation links are currently available, emphasizing the need for proactive defensive measures. Organizations relying on webfsd should audit their environments to identify vulnerable instances and restrict external access until a patch is released. Network-level protections such as web application firewalls (WAFs) and intrusion detection systems (IDS) can help detect and block exploit attempts. Additionally, monitoring logs for anomalous requests targeting the filename parameter can provide early warning of exploitation attempts.

Potential Impact

For European organizations, the impact of CVE-2025-70314 could be significant, especially in sectors that utilize embedded systems or legacy web servers running webfsd 1.21. Successful exploitation could lead to unauthorized remote code execution, allowing attackers to gain control over affected systems, steal sensitive data, or disrupt services. This could affect industrial control systems, IoT devices, or internal web services that rely on webfsd, potentially causing operational downtime or safety risks. The denial of service aspect could interrupt critical business functions or public services. Given the vulnerability requires no authentication and can be triggered remotely, the attack surface is broad, increasing the likelihood of exploitation if the vulnerability becomes publicly known or exploited in the wild. European organizations with limited patch management capabilities or legacy infrastructure are particularly at risk. Furthermore, the lack of current patches means organizations must rely on compensating controls, increasing operational complexity and risk exposure.

Mitigation Recommendations

1. Immediate identification and inventory of all webfsd 1.21 instances within the network, including embedded and legacy systems. 2. Restrict network access to these instances by implementing firewall rules or network segmentation to limit exposure to untrusted networks. 3. Deploy web application firewalls (WAFs) or intrusion prevention systems (IPS) configured to detect and block malformed HTTP requests targeting the filename parameter. 4. Monitor server logs and network traffic for unusual or suspicious requests that could indicate exploitation attempts. 5. Apply patches or updates from the vendor as soon as they become available; if no official patch exists, consider upgrading to alternative, actively maintained web server software. 6. Implement input validation and sanitization at the application or proxy level to prevent buffer overflow attempts. 7. Conduct regular security assessments and penetration testing focused on legacy and embedded systems to identify similar vulnerabilities. 8. Educate IT and security teams about the risks associated with legacy software and the importance of timely patching and network controls.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
mitre
Date Reserved
2026-01-09T00:00:00.000Z
Cvss Version
null
State
PUBLISHED

Threat ID: 698e2eb9c9e1ff5ad808ac25

Added to database: 2/12/2026, 7:49:13 PM

Last enriched: 2/12/2026, 8:04:30 PM

Last updated: 2/21/2026, 12:16:03 AM

Views: 24

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 more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats