dbcve.org
Hybrid Data PipelineApplication · Progress

CVE-2025-6505

HIGH · 8.1 CVSS v3.1 Published 2025-07-29
Fix available
A fix is available. Upgrade to 4.6.2.3275 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Unauthorized access and impersonation can occur in versions 4.6.2.3226 and below of Progress Software's Hybrid Data Pipeline Server on Linux. This vulnerability allows attackers to combine credentials from different sources, potentially leading to client impersonation and unauthorized access.  When OAuth Clients perform an OAuth handshake with the Hybrid Data Pipeline Server, the server accepts client credentials from both HTTP headers and request parameters.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Hybrid Data Pipeline Server accepts OAuth client credentials from both HTTP headers and request parameters during the OAuth handshake. This dual-source credential acceptance allows attackers to mix credentials from different sources, enabling client impersonation and unauthorized access to the server.

MitigationUpgrade to a version above 4.6.2.3226 when available, or apply vendor-supplied patches. In the interim, restrict network access to the OAuth endpoints and implement additional monitoring on authentication attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Hybrid Data PipelineApplication
Affected:< 4.6.2.3275

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Hybrid Data Pipeline installation
    Locate the Hybrid Data Pipeline installation directory and check for version information files or use the product's administrative interface to determine the installed version
    Affected if The installed version is lower than 4.6.2.3275
  2. Verify OAuth endpoint accessibility
    Determine if the OAuth endpoints (typically at /oauth/ token or similar paths) are exposed on the network by reviewing web server configuration or firewall rules
    Affected if OAuth endpoints are accessible from untrusted networks
  3. Check OAuth configuration for dual-source acceptance
    Review the OAuth configuration files or settings to confirm whether the server is configured to accept credentials from both HTTP headers and request parameters simultaneously
    Affected if OAuth is configured to accept credentials from both headers and request parameters
  4. Review authentication logs for credential mixing
    Examine authentication and access logs for OAuth handshake attempts where credentials originate from mixed sources (e.g., client_id in header with client_secret in parameter)
    Affected if Logs show authentication attempts with credentials from different sources

A user is affected if they are running any version of Progress Hybrid Data Pipeline below 4.6.2.3275 with OAuth endpoints accessible and the dual-source credential acceptance configuration in use.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.6.2.3275 or later
Fixed in 4.6.2.3275
Interim mitigation

Upgrade to a version above 4.6.2.3226 when available, or apply vendor-supplied patches. In the interim, restrict network access to the OAuth endpoints and implement additional monitoring on authentication attempts.

Recommended fix Moderate confidence

4.6.2.3275

  1. 1. Back up the current Hybrid Data Pipeline installation and configuration.
  2. 2. Download Progress Hybrid Data Pipeline version 4.6.2.3275 or later from the Progress Software community or official download portal.
  3. 3. Stop the Hybrid Data Pipeline service.
  4. 4. Install the updated version (4.6.2.3275 or newer) following the standard upgrade procedure.
  5. 5. Verify the installation and ensure the service starts successfully.
  6. 6. Test OAuth client connections to confirm the authentication mechanism now properly validates credentials from a single source.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Hybrid Data Pipeline Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-6505 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-6505 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data