CVE-2026-12200: Ritlabs TinyWeb Server Header libeay32.dll.html stack-based overflow
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.
CVE-2026-12200 is a remotely reachable buffer overflow in Ritlabs TinyWeb Server for Win32 through version 1.94. A malicious Authorization header can crash or potentially compromise the service. Public exploit information is referenced, but the provided sources do not show confirmed active exploitation or a vendor fix.
Executive priority
Treat as a high-priority exposure reduction item for any reachable TinyWeb deployment. Public exploit information and no named vendor fix increase operational risk. Prioritize removing, replacing, or isolating affected services rather than waiting for confirmed exploitation.
Technical view
The issue affects TinyWeb Server’s Header Handler, specifically handling of the Authorization argument in libeay32.dll.html. VulDB describes a stack-based buffer overflow with network attack vector, low complexity, no authentication, and partial confidentiality, integrity, and availability impact. CVSS v2 is 7.5. CWE mappings include CWE-119 and CWE-121.
Likely exposure
Exposure is most relevant where Ritlabs TinyWeb Server 1.94 or earlier runs on Win32 and accepts untrusted HTTP traffic. Internet-facing deployments are higher risk. Internal-only services still matter if reachable by untrusted users, compromised hosts, or shared networks.
Exploitation context
The source bundle states the exploit has been publicly disclosed and may be used, with exploitability marked as proof-of-concept. KEV is false, and no cited source confirms active exploitation in the wild. Vendor contact reportedly received no response.
Researcher notes
Evidence is largely from VulDB and the CVE record. The vulnerable function is described as unknown, and the vendor reportedly did not respond. The public exploit reference should be reviewed defensively, but avoid reproducing it on production systems.
Mitigation direction
Identify any Ritlabs TinyWeb Server deployments, especially Win32 versions 1.94 and earlier.
Remove or replace TinyWeb Server where business need is low.
Restrict network access to trusted clients only.
Place affected services behind filtering controls where feasible.
Monitor vendor and CVE sources for official guidance or updates.
Validation and detection
Inventory hosts for Ritlabs TinyWeb Server and recorded version.
Confirm whether the service is reachable from the internet or untrusted networks.
Review web logs for unusual Authorization header activity.
Check vulnerability scanners for CVE-2026-12200 coverage.
Document compensating controls if no patch is available.
Based on public source material and reviewed before publication.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-119: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve
time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
4CVSS vectors
6Timeline events
0ADP providers
6Source links
CVSS vector scores
4 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present,
the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-119 · source CWE mapping
Improper Restriction of Operations within the Bounds of a Memory Buffer
Improper Restriction of Operations within the Bounds of a Memory Buffer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.