Threats / Nostromo / CVE-2019-16278
CVE-2019-16278
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Nostromo nhttpd vulnerability
Nostromo nhttpd contains a directory traversal vulnerability in http_verify() that allows remote code execution on non-chrooted servers.
Verdict
Today item — known-exploited.
A directory traversal flaw in Nostromo nhttpd enables unauthenticated attackers to access files outside the intended web root and execute arbitrary code. The vulnerability is actively exploited in the wild with high exploit probability.
CISA KEV Yes · 2024-11-074EPSS 0.99033 (verify live)5Exploit Weaponized · public PoC6CVSS 9.8 (CISA)3CISA SSVC Exploitation: active · Automatable: yes · Impact: total3
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
817 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2024-11-07).
Probability (EPSS)
EPSS 0.99033 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: Nostromo, nhttpd. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-22 Path Traversal — weakness family: Path traversal / file.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 1851 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a functional/weaponized public exploit). Catalog entries: Metasploit module, nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft HTTP requests with path traversal sequences to bypass directory restrictions in the http_verify() function.
Business
Attackers gain unauthorized file system access to sensitive configuration and application files.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I read or modify files outside the web root, including executable scripts or system binaries.
Business
Confidentiality and integrity of hosted content and server configuration are compromised.
3
Lateral reach — past segmentation narrative 3
Attacker
I upload or execute arbitrary code through the traversal vulnerability on the non-chrooted server.
Business
Complete server compromise enables data theft, malware deployment, and lateral movement within the network.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05