Skip to main content
VulnerabilityPublished

CVE-2026-61526: adonisjs http-server · Cross-site Scripting

Affects adonisjs http-serverSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.1 Medium : upgrade to 9.1.0 or 8.2.1 when convenient.

Data as of 29 Oct 2026, 07:15 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 29 Oct 2026.

What to do

Upgrade adonisjs http-server to 9.1.0 or 8.2.1.

Affected software

ProductAffectedFixed in
adonisjshttp-serverAffected
  • >=9.0.0 <9.1.0
Fixed in
  • 9.1.0
adonisjshttp-serverAffected
  • >=8.0.0-next.0 <8.2.1
Fixed in
  • 8.2.1

AI-suggested

Upgrade affected AdonisJS HTTP Server versions to 8.2.1 or later, or 9.1.0 or later, where the vulnerability is fixed. If upgrading is not immediately possible, implement custom status pages or JSON responses to handle errors instead of relying on the default HTML exception response. Patch status is not explicitly stated in the vendor advisory, but fixed versions are known.

Description

A cross-site scripting (XSS) vulnerability exists in the AdonisJS HTTP Server package versions 8.0.0-next.0 through 8.2.0 and 9.0.0 through 9.0.2. The error.message is directly interpolated into the default HTML exception response without proper escaping, allowing attacker-controlled JavaScript execution when a crafted missing-route URL is accessed and no custom error handling is in place. This issue is fixed in versions 8.2.1 and 9.1.0.

References

Community reviews

Loading reviews…