Read the docs
TI-2026-28871 Aliases CVE-2026-40028GHSA-jpj3-m5q9-54rf

Hayabusa < 3.8.0 XSS via JSON Log Import

Priority LOW 23CWE-79Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
Passive
Attack complexity
Low
Attack requirements
None
Impact type
Cross-site scripting
Confidentiality · integrity · availability
None · None · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-79.

Summary

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00208 10th percentileScored 2026-11-07
Fix Fixed hayabusa (Yamato-Security): 3.8.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
Yamato-Securityhayabusaup to 3.7.03.8.0Patch availableCNA
  • hayabusa VendorYamato-Security Affected up to 3.7.0 Fixed in 3.8.0 Patch available CNA

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:yamato-security:hayabusa:*:*:*:*:*:*:*:*before 3.8.0VulnerableYamato-Security
  • cpe:2.3:a:yamato-security:hayabusa:*:*:*:*:*:*:*:* Versions before 3.8.0 Vulnerable ·Yamato-Security

Remediation

  • Fix · CNA hayabusa (Yamato-Security) Fixed in 3.8.0

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-40028
  2. 2026-10-03 Alias added: GHSA-jpj3-m5q9-54rf

References

Advisory 1

Other 1

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences