Skip to main content
VulnerabilityPublished Updated

CVE-2026-40028: Yamato-Security hayabusa · Cross-site Scripting

Affects Yamato-Security hayabusaSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.1 Medium : upgrade to 3.8.0 when convenient.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 4.0 base score
5.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.8.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Apr 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 yamato-security/hayabusa to 3.8.0.

Affected software

ProductAffectedFixed in
Yamato-SecurityhayabusaAffected
  • <=3.7.0
Fixed in–
GitHubyamato-security/hayabusapkg:github/yamato-security/hayabusaOther threatsAffected
  • <3.8.0
Fixed in
  • 3.8.0

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

AI-suggested

If you cannot patch yet, users should avoid scanning or viewing JSON-exported logs containing untrusted or suspicious Computer field data in hayabusa versions prior to 3.8.0. Monitoring vendor communications for updates is recommended.

Description

Hayabusa versions prior to 3.8.0 contain a cross-site scripting (XSS) vulnerability in its HTML report output that allows an attacker to execute arbitrary JavaScript when a user scans JSON-exported logs containing malicious content in the Computer field. An attacker can inject JavaScript into the Computer field of JSON logs that executes in the forensic examiner's browser session when viewing the generated HTML report, leading to information disclosure or code execution.

References

Community reviews

Loading reviews…