CVE-2025-6504: Progress Software Hybrid Data Pipeline · Unauthorized Access to Sensitive Resources
Affects Progress Software Hybrid Data PipelineSource CVE Database V5
Not known to be exploited · CVSS 8.4 High.
Data as of 26 Oct 2026, 09:08 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 29 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Progress Software Hybrid Data Pipeline | Affected
| Fixed in– |
AI-suggested
European organizations should take immediate steps beyond generic advice: 1) Implement strict validation and sanitization of the X-Forwarded-For header at the application or network edge to prevent spoofing. This can include configuring web/application firewalls or reverse proxies to ignore or overwrite client-supplied XFF headers unless they originate from trusted proxies. 2) Restrict access to HDP Server management interfaces and APIs to trusted networks and enforce multi-factor authentication to reduce the risk from compromised credentials. 3) Monitor logs for anomalous XFF header values and access patterns inconsistent with expected IP ranges. 4) Deploy network segmentation to isolate HDP Servers and limit lateral movement if unauthorized access occurs. 5) Engage with Progress Software for timely patching once available and test updates in controlled environments before deployment. 6) Review and tighten IP whitelisting policies, considering alternative or additional access control mechanisms such as client certificates or token-based authentication. 7) Conduct regular security audits and penetration tests focusing on header manipulation and access control bypass scenarios.
Description
In HDP Server versions below 4.6.2.2978 on Linux, unauthorized access could occur via IP spoofing using the X-Forwarded-For header. Since XFF is a client-controlled header, it could be spoofed, allowing unauthorized access if the spoofed IP matched a whitelisted range. This vulnerability could be exploited to bypass IP restrictions, though valid user credentials would still be required for resource access.