dbcve.org
Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2026-2940

HIGH · 7.3 CVSS v3.1 Published 2026-02-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was determined in Zaher1307 tiny_web_server up to 8d77b1044a0ca3a5297d8726ac8aa2cf944d481b. This affects the function tiny_web_server/tiny.c of the file tiny_web_server/tiny.c of the component URL Handler. This manipulation causes out-of-bounds write. The attack can be initiated remotely. The exploit has been publicly disclosed and may be utilized. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available. The project was informed of the problem early through an issue report but has not responded yet.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Out-of-bounds write vulnerability in the URL Handler function in tiny.c allows remote attackers to write data beyond allocated buffer boundaries. This memory corruption issue in the web server's URL parsing logic could potentially enable code execution or denial of service attacks.

MitigationSince no vendor patch is available, isolate the server from untrusted networks, restrict access to trusted sources only, and consider replacing with a maintained web server solution until the vulnerability is addressed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify tiny.c based web server installation
    Search for binaries or source code files named 'tiny.c', 'tinyhttpd', or similar minimal web server components. Check common locations like /usr/bin/, /usr/local/bin/, or web server directories. Use commands: 'find / -name "tiny*" -type f 2>/dev/null' or 'ps aux | grep -i tiny'
    Affected if A web server derived from tiny.c is installed and running
  2. Determine the installed version
    If a tiny.c-based server is found, check its version via: './server --version', 'httpd -v', or inspect the source file header comments in tiny.c. Compare against any available version information from the vendor or project maintainer
    Affected if The installed version cannot be determined or is older than the latest patched release
  3. Verify URL handler is enabled
    Confirm the web server is configured to process HTTP requests by checking if it binds to a network port (common: 80, 8080). Use 'netstat -tlnp' or 'ss -tlnp' to identify listening ports. Review server configuration files for URL routing or handling directives
    Affected if The server is listening on a network port and accepting HTTP requests
  4. Check network exposure
    Examine firewall rules (iptables -L, ufw status) and server bind address configuration. Determine if the web server is accessible from external/untrusted networks or bound to 0.0.0.0 versus localhost only
    Affected if The server is accessible from untrusted network interfaces (0.0.0.0) without network-level filtering
  5. Inspect URL parsing configuration
    Review server configuration for URL handling settings, particularly any custom URL handlers, CGI configurations, or rewrite rules that invoke the URL parsing logic in tiny.c
    Affected if URL parsing functionality is actively used by the server configuration

A user is affected if they have a tiny.c-based web server running that processes URL requests from untrusted network sources, particularly if the server version cannot be confirmed as patched.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since no vendor patch is available, isolate the server from untrusted networks, restrict access to trusted sources only, and consider replacing with a maintained web server solution until the vulnerability is addressed.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2940 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2940 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data