HIGH 7.3

CVE-2026-12200: TinyWeb Server Stack Buffer Overflow in Authorization Header

TinyWeb Server version 1.94 and earlier on Windows contains a stack-based buffer overflow vulnerability in how it processes the Authorization header. An attacker can send a specially crafted HTTP request with a malicious Authorization header to overflow the server's memory and potentially execute code, crash the service, or access sensitive data. The vulnerability requires no authentication or user interaction to exploit, making it actionable for remote attackers.

Source data · NVD / CISA · public domain

CVSS
3.1 · 7.3 HIGH · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Weaknesses (CWE)
CWE-119, CWE-121
Affected products
0 configuration(s)
Published / Modified
2026-06-15 / 2026-06-17

NVD description (verbatim)

A security vulnerability has been detected in Ritlabs TinyWeb Server up to 1.94 on Win32. This impacts an unknown function in the library libeay32.dll.html of the component Header Handler. The manipulation of the argument Authorization leads to stack-based buffer overflow. The attack can be initiated remotely. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

5 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-12200 is a stack-based buffer overflow (CWE-121) introduced via improper input validation (CWE-119) in the Header Handler component of Ritlabs TinyWeb Server affecting version 1.94 and prior. The vulnerability resides in the processing of the Authorization HTTP header field. An attacker crafting an oversized or malformed Authorization header can trigger memory corruption, bypassing bounds checking in the libeay32.dll.html library component on Win32 systems. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L) reflects remote exploitability with low attack complexity and no privilege or user interaction requirements.

Business impact

Organizations running TinyWeb Server 1.94 for web hosting, file serving, or embedded applications face immediate risk of service disruption, data exfiltration, and potential code execution under the context of the web server process. The public disclosure and vendor non-responsiveness mean exploit tooling may become readily available, lowering the barrier for opportunistic attacks. Affected services may be rapidly compromised without evidence of legitimate authentication, increasing incident investigation complexity.

Affected systems

Ritlabs TinyWeb Server version 1.94 and all prior versions on Win32 (32-bit Windows) platforms are affected. No patched version has been indicated by the vendor. Organizations should conduct an asset inventory to identify TinyWeb Server instances in development, production, test, and legacy environments, including embedded or discontinued deployments that may still be accessible.

Exploitability

This vulnerability has a CVSS score of 7.3 (HIGH) and is classified as non-networked exploitation with minimal complexity. Public exploit disclosure has occurred, and the vendor has not responded to early disclosure attempts, meaning defensive patches are unlikely to emerge promptly. The attack surface is broad: any system accepting HTTP connections is at risk if TinyWeb Server is running. Exploitation requires only network access and knowledge of the vulnerable header parsing behavior—no specialized tools or elevated privileges are necessary.

Remediation

Immediate mitigation includes discontinuing or isolating affected TinyWeb Server instances from untrusted networks. Verify against the vendor advisory and monitor Ritlabs channels for a security update; however, given the non-responsive posture, consider alternative web server software (Apache, Nginx, IIS) for mission-critical deployments. If TinyWeb Server cannot be immediately replaced, implement network-level filtering to block or sanitize HTTP Authorization headers at a perimeter firewall or web application firewall, though this is not a substitute for patching.

Patch guidance

As of the published date, no vendor patch has been released or announced. Organizations should monitor the official Ritlabs TinyWeb Server website and security advisories for updates. If a patch becomes available, test it in a non-production environment before deployment. Given vendor non-responsiveness, evaluate the long-term viability of TinyWeb Server for your infrastructure and plan a migration timeline to a maintained alternative.

Detection guidance

Monitor web server logs for HTTP requests containing unusually long or malformed Authorization headers, particularly those exceeding expected RFC 7235 lengths (typically under 500 bytes). Implement network intrusion detection signatures targeting oversized header payloads to TinyWeb Server instances. Enable Windows event logging and memory protection features (DEP/ASLR) where possible to detect and log buffer overflow exploitation attempts. Correlate web server process crashes or unexpected restarts with preceding HTTP requests.

Why prioritize this

This vulnerability merits immediate attention due to its combination of remote exploitability, high CVSS score (7.3), public exploit availability, and vendor non-responsiveness. It requires no authentication or user interaction, giving attackers a wide attack surface. Organizations with exposed TinyWeb Server instances face imminent compromise risk and should treat this as a critical remediation priority.

Risk score, explained

The CVSS 3.1 score of 7.3 reflects a HIGH-severity vulnerability with remote network exploitability (AV:N), low attack complexity (AC:L), and no authentication or user interaction requirement (PR:N/UI:N). The attack impacts confidentiality, integrity, and availability at the individual scope level, aligning with the immediate threat posed by stack-based buffer overflow. Absent a vendor security update and with public disclosure, the practical risk to organizations running affected versions is elevated beyond the baseline score.

Frequently asked questions

Is there a vendor patch available for CVE-2026-12200?

No. As of the disclosure date, Ritlabs has not released a security update, and the vendor did not respond to early disclosure attempts. Monitor official Ritlabs channels for updates, but plan for alternative mitigation or product replacement.

Can this vulnerability be exploited without network access?

No. The vulnerability requires remote network access to send a crafted HTTP Authorization header to the TinyWeb Server. It cannot be exploited locally or offline.

What versions of TinyWeb Server are affected?

Version 1.94 and all prior versions on Win32 platforms are vulnerable. If you are running TinyWeb Server, verify your version against the official product documentation and assume all versions up to 1.94 are at risk.

If I must keep TinyWeb Server running, what interim controls help?

Network segmentation and firewall rules to restrict HTTP access to trusted sources only are essential. Web application firewalls (WAF) can inspect and reject Authorization headers exceeding expected sizes. However, these are temporary measures and do not address the underlying flaw—prioritize migration to a patched or actively maintained web server.

This analysis is provided for informational purposes and represents the state of threat intelligence as of the publication date. No exploit code, proof-of-concept, or weaponized instructions are provided herein. Organizations should verify all technical details, patch status, and affected version numbers against official vendor advisories and security bulletins before making remediation decisions. The CVSS score, CWE classifications, and vendor response status are accurate as published; however, situations may change. Conduct your own security assessment and consult with your security team and vendor before implementing any mitigations. Source: NVD (public-domain), retrieved 2026-07-20. Analysis generated by SEC.co (claude-haiku-4-5).