CVE-2026-40028
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedHayabusa 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceHayabusa versions prior to 3.8.0 have a stored XSS vulnerability in HTML report generation. When JSON logs containing malicious JavaScript in the Computer field are processed into HTML reports, the unsanitized input is rendered directly in the browser, allowing arbitrary script execution in the forensic examiner's session.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 3.8.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Hayabusa versionRun 'hayabusa --version' or check the binary metadata to determine the installed version numberAffected if Version is below 3.8.0
-
Verify HTML report generation is usedCheck if Hayabusa is configured to output HTML reports using the --html or -H flag, or review saved report generation configurationsAffected if HTML report generation is enabled and being used
-
Identify JSON log sources with Computer fieldReview the JSON log sources or data feeds being processed by Hayabusa to identify if they contain a Computer field in the log entriesAffected if JSON logs contain a Computer field that gets included in HTML reports
-
Inspect generated HTML reports for unsanitized contentOpen generated HTML report files in a text editor and search for the Computer field values to see if any contain script tags, JavaScript event handlers, or other HTML/script contentAffected if Computer field contains unsanitized HTML or JavaScript code
User is affected if running Hayabusa version below 3.8.0 and generating HTML reports from JSON logs containing a Computer field that may contain injected scripts
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.8.0
Upgrade to Hayabusa version 3.8.0 or later which implements proper input sanitization for the Computer field in HTML report generation to prevent XSS.
Hayabusa 3.8.0
- Verify current Hayabusa version by running 'hayabusa --version'
- Backup any existing configurations and custom rules in the Hayabusa installation directory
- Download Hayabusa version 3.8.0 from the official GitHub releases page (github.com/Yamato-Security/hayabusa/releases)
- Extract the new version to your desired installation directory
- Replace old binary with the new version 3.8.0 binary
- Verify the upgrade was successful by running 'hayabusa --version' and confirming it shows 3.8.0
- Regenerate HTML reports from previously scanned JSON logs to verify the XSS vulnerability is patched in the output
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-40028 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-40028 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data