CVE-2026-21790: HCLSoftware Traveler · Origin Validation Error
Affects HCLSoftware TravelerSource CVE Database V5
Not known to be exploited · CVSS 6.3 Medium : upgrade to 14.5.1.0 when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 14.5.1.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 24 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade HCLSoftware Traveler to 14.5.1.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| HCLSoftwareTraveler | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, administrators should implement strict HTTP header validation rules at the web server or application gateway level to enforce proper origin checks and reject suspicious or malformed headers. Network segmentation and strict access controls should limit who can authenticate to the Traveler service, reducing the pool of potential attackers. Monitoring and logging of authentication attempts and HTTP header anomalies can help detect exploitation attempts early. Additionally, organizations should review and tighten any custom authentication or authorization mechanisms integrated with Traveler to ensure they do not rely solely on HTTP headers for security decisions. Security teams should also conduct regular vulnerability assessments and penetration testing focused on web application security controls to identify similar weaknesses proactively.
Description
HCL Traveler is susceptible to a weak default HTTP header validation vulnerability, which could allow an attacker to bypass additional authentication checks.