How severe is CVE-2019-19029?

CVE-2019-19029 has a CVSS score of 7.2/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2019-19029?

CVE-2019-19029 affects the following packages: github.com/goharbor/harbor (Go), github.com/goharbor/harbor (Go). Ecosystems affected: Go.

How do I fix CVE-2019-19029?

Update github.com/goharbor/harbor to 1.8.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-19029 is resolved across your whole dependency graph.

How do I detect CVE-2019-19029 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/goharbor/harbor, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2019-19029 if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is CVE-2019-19029 actively exploited in the wild?

No public exploit code has been indexed for CVE-2019-19029 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2019-19029?

CVE-2019-19029 has an EPSS (Exploit Prediction Scoring System) score of 2.1%, placing it in the 81th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2019-19029?

CVE-2019-19029 is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2019-19029 published, and has it been updated?

CVE-2019-19029 was published on March 20, 2020 and was last updated on August 7, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

HIGH severity

CVE-2019-19029 — harbor

HIGH

CVE-2019-19029 is a high-severity (CVSS 7.2) SQL Injection vulnerability in github.com/goharbor/harbor. A fix is available for github.com/goharbor/harbor — see the affected versions and patch details below.

SQL Injection in Cloud Native Computing Foundation Harbor

Also known asGHSA-jr34-mff8-pc6f GHSA-qcfv-8v29-469wGO-2022-0853

Published

Mar 20, 2020

Updated

Aug 7, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Oct 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs81th percentile — riskier than 81% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2019-19029 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs affected

🐹github.com/goharbor/harbor🐹github.com/goharbor/harbor

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Cloud Native Computing Foundation Harbor prior to 1.8.6 and 1.9.3 allows SQL Injection via user-groups in the VMware Harbor Container Registry for the Pivotal Platform.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/goharbor/harbor`	≥ 1.7.0&&< 1.8.6	1.8.6`go get github.com/goharbor/harbor@v1.8.6`
🐹Go	`github.com/goharbor/harbor`	≥ 1.9.0&&< 1.9.3	1.9.3`go get github.com/goharbor/harbor@v1.9.3`

Affected Products

2 products · 3 configurations

Application

harborlinuxfoundation

≥ 1.9.0 && < 1.9.3

range

Application

vmware harbor registrypivotal

all

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/goharbor/harbor, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/goharbor/harbor to 1.8.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-19029 is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Frequently Asked Questions

Cloud Native Computing Foundation Harbor prior to 1.8.6 and 1.9.3 allows SQL Injection via user-groups in the VMware Harbor Container Registry for the Pivotal Platform.

O3 Security · Impact-Aware SCA

Is CVE-2019-19029 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.2/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

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

CWE Classification

CWE-89SQL Injection

Weaponization

No known public exploit tooling found.

OpenSSF Scorecard

Package health score

harbor

7.4/10

Code-Review4/10

Maintained10/10

Branch-ProtectionN/A

Assessed Oct 5, 2026

Timeline

Disclosed

Mar 20, 2020

Last updated

Aug 7, 2026

Identifiers

CVE-2019-19029

GHSA-jr34-mff8-pc6f

GO-2022-0853

References

Advisorygithub.com Advisorygithub.com Advisorytanzu.vmware.com Advisorynvd.nist.gov Webpkg.go.dev Packagegithub.com

Related vulnerabilities

This CVE is high severity; 3 of 8 other CVEs affecting harbor are rated as high or higher (top: critical).

GHSA-prh4-vhfh-24mjCVE-2026-4404CVE-2025-32019CVE-2025-30086CVE-2022-31668CVE-2024-22278CVE-2024-22244CVE-2024-22261

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedAug 7, 2026

CVE-2019-19029 — harbor

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2019-19029 in your dependencies?