Partial String Comparison Vulnerability in HiRDB
- Exploited
- No known exploitation
- Fix
- Fixed in 10-11-02
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 10-11-02.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.39% · 32nd percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 30/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
A partial string comparison flaw in HiRDB Server, including the Additional Function editions, can let a remote attacker without logging in and without any user action compromise confidentiality, integrity, and availability. The flaw is reachable over the network with no authentication required.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Partial String Comparison Vulnerability in HiRDB.
This issue affects HiRDB Server Version 10: from 10-00 before 10-12-01; HiRDB Server Version 9: from 09-50-06 through 09-66-22; HiRDB Server with Additional Function Version 9: from 09-50-/F through 09-66/V; HiRDB Server Version 9(32): from 09-50-06 through 09-66-22; HiRDB Server with Additional Function Version 9(32): from 09-50-/F through 09-66-/V.
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.8, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 35 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 10-11-02.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-115646 (Partial String Comparison Vulnerability in HiRDB), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-115646 (entry last updated 2026-11-10): Affected: - Hitachi HiRDB Server Version 10: from 10-00, fixed in 10-11-02 - Hitachi HiRDB Server Version 9: from 09-50-06, through 09-66-22 - Hitachi HiRDB Server with Additional Function Version 9: from 09-50-/F, through 09-66/V - Hitachi HiRDB Server Version 9(32): from 09-50-06, through 09-66-22 - Hitachi HiRDB Server with Additional Function Version 9(32): from 09-50-/F, through 09-66-/V Fixed versions: 10-11-02. Conditions (all must be true for the bug to be hit): - Runs an affected HiRDB Server version listed in the advisory (Version 10 from 10-00 up to 10-12-01, and listed Version 9 and 9(32) releases, including the with Additional Function variants) (source: https://www.hitachi.com/products/it/software/security/info/vuls/hitachi-sec-2026-165/index.html) Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. Attacker needs: network access, no login, no user action. CISA KEV: CVE-2026-115646 is not listed as of cve.now's last read. This KEV status is for CVE-2026-115646 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://www.hitachi.com/products/it/software/security/info/vuls/hitachi-sec-2026-165/index.html Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-115646 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-115646.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- Hitachi HiRDB Server Version 10
From 10-00 · fixed in 10-11-02
- Hitachi HiRDB Server Version 9
From 09-50-06 · through 09-66-22
- Hitachi HiRDB Server with Additional Function Version 9
From 09-50-/F · through 09-66/V
- Hitachi HiRDB Server Version 9(32)
From 09-50-06 · through 09-66-22
- Hitachi HiRDB Server with Additional Function Version 9(32)
From 09-50-/F · through 09-66-/V
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-115646
Is CVE-2026-115646 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The advisory describes a partial string comparison flaw in HiRDB Server, and the facts give no further detail on how it works. The CVSS 9.8 base score in the advisory rates the impact as high for confidentiality, integrity and availability.Source: hitachi.com
Which versions are affected by CVE-2026-115646?
HiRDB Server Version 10: from 10-00 before 10-11-02. HiRDB Server Version 9: from 09-50-06 through 09-66-22. HiRDB Server with Additional Function Version 9: from 09-50-/F through 09-66/V. HiRDB Server Version 9(32): from 09-50-06 through 09-66-22. HiRDB Server with Additional Function Version 9(32): from 09-50-/F through 09-66-/V.Source: cve.now feed data
Am I affected, and how do I check?
The advisory lists HiRDB Server Version 10 from 10-00 with a fixed release of 10-11-02, and HiRDB Server Version 9 and 9(32) from 09-50-06 through 09-66-22, plus the with Additional Function variants of Version 9 and 9(32). The condition text gives the Version 10 range as up to 10-12-01, which does not match the 10-11-02 fixed value, so check the advisory's own table. To check a installation, compare its HiRDB Server version number against these listed ranges.Source: hitachi.com
How do I fix CVE-2026-115646?
For Version 10, the advisory's fixed value is 10-11-02, so move to 10-11-02 or later. The facts give no fixed release for the listed Version 9 and 9(32) lines, so consult the advisory for the remedy on those versions.Source: hitachi.com