API-surface disclosure via public Swagger documentation
Published Aug 24, 2026 · Updated Aug 24, 2026
Information exposure in HCL Hive 1.0 allows remote attackers to view Swagger API documentation without authentication. The deployed web interface serves its Swagger documentation to unauthenticated requests instead of enforcing access control, exposing API endpoints and request structures. Network reachability and interaction with the documentation endpoint are required; HCL reports no credentials or PII in the exposed material, so the direct impact is API-surface disclosure.
Summary
What happened
Information exposure in HCL Hive 1.0 allows remote attackers to view Swagger API documentation without authentication. The deployed web interface serves its Swagger documentation to unauthenticated requests instead of enforcing access control, exposing API endpoints and request structures. Network reachability and interaction with the documentation endpoint are required; HCL reports no credentials or PII in the exposed material, so the direct impact is API-surface disclosure.
The record
- CVE
- CVE-2026-21759
- Published
- Aug 24, 2026
- Updated
- Aug 24, 2026
- Vendor
- HCLSoftware
- Product
- HCL Hive
- Classifications
- CWE-215, T1595
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 24, 2026CVE publishedPublication date reported by the CVE source.
- Aug 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo