← Vulnerability feed

Vulnerability record · CVE-2006-5216 · published 10 October 2006

CVE-2006-5216: Simple HTTPD stack buffer overflow via long URI

SSergey Lyubka · Simple Httpd

Sergey Lyubka Simple HTTPD (shttpd) 1.34 has a stack-based buffer overflow that is triggered by an overly long request URI. Because the flaw is reachable over the network without authentication, it exposes the web server process to remote code execution.

7.5 CVSS 2.0 High EPSS 64% · top 0.8%
7.5CVSS 2.0 base score
64%EPSS exploitation probability, 30 days
NoNot in CISA KEV
1Affected product versions listed by NVD
16References
16 Jun 2026Last modified by NVD

Description

Stack-based buffer overflow in Sergey Lyubka Simple HTTPD (shttpd) 1.34 allows remote attackers to execute arbitrary code via a long URI.

AV:N/AC:L/Au:N/C:P/I:P/A:P

Automated analysis

Generated by VULONE's analysis model from the NVD record, CISA KEV and EPSS data on 19 September 2026. Confidence: medium.

high priorityThe flaw is remotely exploitable without authentication, has a high CVSS v2 score of 7.5, and public exploit code exists, though it is not in CISA KEV.

What it is

Sergey Lyubka Simple HTTPD (shttpd) 1.34 has a stack-based buffer overflow that is triggered by an overly long request URI. Because the flaw is reachable over the network without authentication, it exposes the web server process to remote code execution.

Impact

A remote attacker can corrupt the stack and potentially execute arbitrary code in the context of the shttpd process, which may lead to full compromise of the host or service.

Attack surface

The flaw is reached over the network through an HTTP request containing a long URI, as reflected by the AV:N/AC:L/Au:N vector. No authentication or user interaction is required.

Exploitation

CVE-2006-5216 is not listed in CISA KEV, but EPSS is very high at 0.63645 (99.18th percentile), and public references include an Exploit-DB entry, indicating exploit code is publicly available.

What to do

  • Upgrade shttpd to a version later than 1.34 if one is available from the vendor.
  • If upgrading is not possible, place shttpd behind a reverse proxy or WAF that rejects abnormally long request URIs.
  • Restrict network access to the shttpd listener to trusted clients only.
  • Run shttpd with least privilege and isolate it from sensitive data and systems.

Detection

  • Monitor web server and proxy logs for HTTP requests with unusually long URI values.
  • Alert on crashes or restarts of the shttpd process.
  • Use network IDS signatures for long-URI buffer overflow attempts against shttpd.

This assessment is produced automatically and is not human-reviewed. Verify against the vendor advisory before acting on it.

Affected products

1 vulnerable configurations from NVD's CPE data, grouped by vendor and product.

References

Track CVE-2006-5216 inside VULONE

Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.

Start free Open in platform

Related vulnerabilities

Same products first, then exploited flaws of the same weakness class.

Source: NIST National Vulnerability Database (record CVE-2006-5216), CISA KEV, FIRST EPSS (scores of 2026-09-26). This page is refreshed as NVD updates the record.