Security readout for executives and security teams
Plain-English summary
A remote, unauthenticated attacker could abuse SVG processing in affected Bold Reports servers to read arbitrary local files. Exposed configuration files or credentials could enable application takeover and broader compromise. The vulnerable DataHub component first appeared in version 6.3; earlier versions are stated not to be affected.
Executive priority
Treat internet-accessible affected deployments as an immediate remediation priority. File disclosure can expose credentials and turn one application weakness into wider unauthorized access. Prioritize inventory, vendor-confirmed upgrading, access restriction, incident review, and secret rotation where exposure cannot be excluded.
Technical view
CVE-2026-65687 is a CWE-22 filepath-validation failure in the DataHub SVG-processing feature. Crafted requests can traverse intended filesystem boundaries and disclose files readable by the application account. The supplied CVSS 3.1 score is 9.8, with network access, low complexity, no privileges, and no user interaction.
Likely exposure
Highest risk applies to network-accessible Standalone Report Designer deployments running DataHub from version 6.3 through releases before 14.1.12. Exposure depends on reachability and application-account file permissions. The supplied affected-version list inconsistently includes 14.1.12, so organizations should verify their exact build against vendor guidance.
Exploitation context
The vulnerability is remotely reachable and requires neither authentication nor user interaction. The bundle marks it as absent from KEV and provides no cited evidence of active exploitation. Its characteristics nevertheless make exposed systems attractive targets because file disclosure may reveal reusable credentials.
Researcher notes
The bundle conflicts on version boundaries: its title and description say releases before 14.1.12, while the affected list includes 14.1.12. It also describes arbitrary file read, although the CVSS vector claims high integrity and availability impact. Confirm both details with the vendor before final asset classification.
Mitigation direction
- Inventory reachable Standalone Report Designer deployments and determine whether DataHub is installed and enabled.
- Upgrade affected deployments to 14.1.12 or a later vendor-confirmed fixed release.
- Until upgraded, restrict untrusted network access to the designer and DataHub functionality.
- Investigate potential exposure, then rotate credentials and secrets stored on affected servers.
Validation and detection
- Confirm the exact installed version and whether the deployment includes DataHub.
- Verify the vendor classifies the deployed build as fixed, particularly because 14.1.12 is inconsistently listed.
- Review application and reverse-proxy logs for unexpected unauthenticated SVG-processing activity.
- Identify sensitive files readable by the application account and assess resulting credential exposure.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-65687 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- Release NotesCVE reference, VulnCheck · release-notes
- https://www.vulncheck.com/advisories/bold-reports-standalone-report-designer-arbitrary-file-read-via-svg-processingCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.