Possible ORM Leak Vulnerability in the Harbor

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2025-30086: 0.71% estimated exploitation activity in the next 30 days; percentile 53.75 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact Administrator users on Harbor could exploit an ORM Leak (https://www.elttam.com/blog/plormbing-your-django-orm/) vulnerability that was present in the /api/v2.0/users endpoint to leak users' password hash and salt values. This vulnerability was introduced into the application because the q URL parameter allowed the administrator to filter users by any column, and the filter password=~ could be abused to leak out a user's password hash character by character. An attacker with administrator access could exploit this vulnerability to leak highly sensitive information stored on the Harbor database, as demonstrated in the attached writeup by the leaking of users' password hashes and salts. All endpoints that support the q URL parameter are vulnerable to this ORM leak attack, and could potentially be exploitable by lower privileged users to gain unauthorised access to other sensitive information. Patches No available Workarounds NA References Credit alex@elttam.com

Published by the source

23 Jul 2025, 15:47 UTC

Last modified by the source

25 Jul 2025, 20:02 UTC

Source last checked

26 Oct 2026, 15:09 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-h27m-3qw8-3pw8

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-30086

Advisory: Possible ORM Leak Vulnerability in the Harbor
IDs: CVE-2025-30086, GHSA-h27m-3qw8-3pw8
Record: https://patchnext.com/advisories/cve-2025-30086 (revision 1, source checked 26 Oct 2026, 15:09 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/goharbor/harbor 2.13.1, 2.12.4, 2.4.0-rc1.0.20250331071157-dce7d9f5cffb. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/goharbor/harbor: affected >= 2.13.0, <= 2.13.0; >= 2.4.0-rc1.1, < 2.12.4; < 2.4.0-rc1.0.20250331071157-dce7d9f5cffb; fixed in 2.12.4, 2.13.1, 2.4.0-rc1.0.20250331071157-dce7d9f5cffb

## Suggested inspection (read-only)
- Go github.com/goharbor/harbor: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/goharbor/harbor.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-h27m-3qw8-3pw8 (GitHub-reviewed advisory GHSA-h27m-3qw8-3pw8 lists affected ranges: Go github.com/goharbor/harbor >=2.13.0 =2.4.0-rc1.1 =0 <2.4.0-rc1.0.20250331071157-dce7d9f5cffb)

Commands are suggestions: review each one before running it.