Skip to main content
VulnerabilityPublished Updated

CVE-2026-50018: SpectoLabs hoverfly · Uncontrolled Resource Consumption

Affects SpectoLabs hoverflySource CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium : upgrade to 1.12.8 when convenient.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.12.8
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade hoverfly and github.com/spectolabs/hoverfly to 1.12.8.

Affected software

ProductAffectedFixed in
SpectoLabshoverflyAffected
  • <1.12.8
Fixed in
  • 1.12.8
Gogithub.com/spectolabs/hoverflypkg:golang/github.com/spectolabs/hoverflyOther threatsAffected
  • <1.12.8
Fixed in
  • 1.12.8

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to SpectoLabs hoverfly version 1.12.8 or later, where the issue is patched by adding timeout configuration to the HTTP client used in remote post-serve actions.

Description

Hoverfly is an open source API simulation tool. Prior to version 1.12.8, remote post-serve actions use `http.DefaultClient` without any timeout configuration. When the remote endpoint is unreachable or intentionally slow (accepts TCP connection but never responds), each triggered proxy request spawns a goroutine that blocks indefinitely on `http.DefaultClient.Do()`. An attacker can cause unbounded goroutine accumulation leading to memory exhaustion and process crash (OOM kill). Unlike local post-serve action execution, this requires no binary execution, only a URL pointing to a non-responsive endpoint. Version 1.12.8 patches the issue.

References

Community reviews

Loading reviews…