CVE-2019-19026 json
SQL Injection in Cloud Native Computing Foundation Harbor
published 6y ago modified 4mo ago also GHSA-rh89-vvrg-fg64 , GHSA-w4x5-jqq4-qc8x , GO-2022-0883 , EUVD-2021-1209
- cvss
- 4.9
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 73%
- public exploits
- 0
- none known
Summary
Cloud Native Computing Foundation Harbor prior to 1.8.6 and 1.9.3 allows SQL Injection via project quotas in the VMware Harbor Container Registry for the Pivotal Platform.
Patch / fix
- go github.com/goharbor/harbor 1.8.6, 1.9.3
- linuxfoundation harbor 1.8.6, 1.9.3
Is CVE-2019-19026 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.42% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 4.9 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
| GitHub | 3.1 | 4.9 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/goharbor/harbor | >=1.7.0, <1.8.6 >=1.9.0, <1.9.3 |
1.8.6 1.9.3 |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
github.com
/goharbor/harbor/security/advisories
web, third-party-advisory
-
tanzu.vmware.com
/security/cve-2019-19026
web, third-party-advisory
-
github.com
/goharbor/harbor/security/advisories/GHSA-rh89-vvrg-fg64
web, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-19026
advisory
-
github.com
/advisories/GHSA-w4x5-jqq4-qc8x
advisory
Sources
- CVE List CVE-2019-19026
- GitHub Advisory GHSA-w4x5-jqq4-qc8x
- NVD CVE-2019-19026
- OSV GO-2022-0883
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.