Bitnami package
harbor
pkg:bitnami/harbor
Vulnerabilities (16)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2026-4404 | Cri | 9.4 | < 2.15.1 | 2.15.1 | Mar 23, 2026 | Use of hard coded credentials in GoHarbor Harbor version 2.15.0 and below, allows attackers to use the default password and gain access to the web UI. | |
| CVE-2025-32019 | Med | 4.1 | < 2.11.3 | 2.11.3 | Jul 23, 2025 | Harbor is an open source trusted cloud native registry project that stores, signs, and scans content. Versions 2.11.2 and below, as well as versions 2.12.0-rc1 and 2.13.0-rc1, contain a vulnerability where the markdown field in the info tab page can be exploited to inject XSS cod | |
| CVE-2022-31671 | Hig | 7.4 | >= 2.0.0, < 2.4.3 | 2.4.3 | Nov 14, 2024 | Harbor fails to validate user permissions when reading and updating job execution logs through the P2P preheat execution logs. By sending a request that attempts to read/update P2P preheat execution logs and specifying different job IDs, malicious authenticated users could read a | |
| CVE-2022-31670 | Hig | 7.7 | >= 1.0.0, < 1.10.13 | 1.10.13 | Nov 14, 2024 | Harbor fails to validate the user permissions when updating tag retention policies. By sending a request to update a tag retention policy with an id that belongs to a project that the currently authenticated user doesn’t have access to, the attacker could modify tag retention p | |
| CVE-2022-31669 | Med | 6.4 | >= 2.0.0, < 2.4.3 | 2.4.3 | Nov 14, 2024 | Harbor fails to validate the user permissions when updating tag immutability policies. By sending a request to update a tag immutability policy with an id that belongs to a project that the currently authenticated user doesn’t have access to, the attacker could modify tag immut | |
| CVE-2022-31668 | Hig | 7.4 | >= 2.0.0, < 2.4.3 | 2.4.3 | Nov 14, 2024 | Harbor fails to validate the user permissions when updating p2p preheat policies. By sending a request to update a p2p preheat policy with an id that belongs to a project that the currently authenticated user doesn't have access to, the attacker could modify p2p preheat policies | |
| CVE-2022-31667 | Med | 6.4 | >= 2.0.0, < 2.4.3 | 2.4.3 | Nov 14, 2024 | Harbor fails to validate the user permissions when updating a robot account that belongs to a project that the authenticated user doesn’t have access to. By sending a request that attempts to update a robot account, and specifying a robot account id and robot account name that | |
| CVE-2022-31666 | Hig | 7.7 | >= 2.0.0, < 2.4.3 | 2.4.3 | Nov 14, 2024 | Harbor fails to validate user permissions while deleting Webhook policies, allowing malicious users to view, update and delete Webhook policies of other users. The attacker could modify Webhook policies configured in other projects. | |
| CVE-2024-22278 | Med | 6.4 | < 2.11.0 | 2.11.0 | Aug 2, 2024 | Incorrect user permission validation in Harbor <v2.9.5 and Harbor <v2.10.3 allows authenticated users to modify configurations. | |
| CVE-2024-22261 | Low | 2.7 | >= 2.8.1, < 2.8.6 | 2.8.6 | Jun 11, 2024 | SQL-Injection in Harbor allows priviledge users to leak the task IDs | |
| CVE-2024-22244 | Med | 4.3 | >= 2.8.0, < 2.10.1 | 2.10.1 | Jun 10, 2024 | Open Redirect in Harbor <=v2.8.4, <=v2.9.2, and <=v2.10.0 may redirect a user to a malicious site. | |
| CVE-2023-20902 | Med | 5.9 | < 1.10.17 | 1.10.17 | Nov 9, 2023 | A timing condition in Harbor 2.6.x and below, Harbor 2.7.2 and below, Harbor 2.8.2 and below, and Harbor 1.10.17 and below allows an attacker with network access to create jobs/stop job tasks and retrieve job task information. | |
| CVE-2022-46463 | Hig | 7.5 | >= 1.1.0, < 2.5.4 | 2.5.4 | Jan 13, 2023 | An access control issue in Harbor v1.X.X to v2.5.3 allows attackers to access public and private image repositories without authentication. NOTE: the vendor's position is that this "is clearly described in the documentation as a feature." | |
| CVE-2020-29662 | Med | 5.3 | >= 2.0.0, < 2.0.5 | 2.0.5 | Feb 2, 2021 | In Harbor 2.0 before 2.0.5 and 2.1.x before 2.1.2 the catalog’s registry API is exposed on an unauthenticated path. | |
| CVE-2020-13794 | Med | 4.3 | >= 1.9.0, < 2.0.3 | 2.0.3 | Sep 30, 2020 | Harbor 1.9.* 1.10.* and 2.0.* allows Exposure of Sensitive Information to an Unauthorized Actor. | |
| CVE-2020-13788 | Med | 4.3 | < 2.0.1 | 2.0.1 | Jul 15, 2020 | Harbor prior to 2.0.1 allows SSRF with this limitation: an attacker with the ability to edit projects can scan ports of hosts accessible on the Harbor server's intranet. |
- affected < 2.15.1fixed 2.15.1
Use of hard coded credentials in GoHarbor Harbor version 2.15.0 and below, allows attackers to use the default password and gain access to the web UI.
- affected < 2.11.3fixed 2.11.3
Harbor is an open source trusted cloud native registry project that stores, signs, and scans content. Versions 2.11.2 and below, as well as versions 2.12.0-rc1 and 2.13.0-rc1, contain a vulnerability where the markdown field in the info tab page can be exploited to inject XSS cod
- affected >= 2.0.0, < 2.4.3fixed 2.4.3
Harbor fails to validate user permissions when reading and updating job execution logs through the P2P preheat execution logs. By sending a request that attempts to read/update P2P preheat execution logs and specifying different job IDs, malicious authenticated users could read a
- affected >= 1.0.0, < 1.10.13fixed 1.10.13
Harbor fails to validate the user permissions when updating tag retention policies. By sending a request to update a tag retention policy with an id that belongs to a project that the currently authenticated user doesn’t have access to, the attacker could modify tag retention p
- affected >= 2.0.0, < 2.4.3fixed 2.4.3
Harbor fails to validate the user permissions when updating tag immutability policies. By sending a request to update a tag immutability policy with an id that belongs to a project that the currently authenticated user doesn’t have access to, the attacker could modify tag immut
- affected >= 2.0.0, < 2.4.3fixed 2.4.3
Harbor fails to validate the user permissions when updating p2p preheat policies. By sending a request to update a p2p preheat policy with an id that belongs to a project that the currently authenticated user doesn't have access to, the attacker could modify p2p preheat policies
- affected >= 2.0.0, < 2.4.3fixed 2.4.3
Harbor fails to validate the user permissions when updating a robot account that belongs to a project that the authenticated user doesn’t have access to. By sending a request that attempts to update a robot account, and specifying a robot account id and robot account name that
- affected >= 2.0.0, < 2.4.3fixed 2.4.3
Harbor fails to validate user permissions while deleting Webhook policies, allowing malicious users to view, update and delete Webhook policies of other users. The attacker could modify Webhook policies configured in other projects.
- affected < 2.11.0fixed 2.11.0
Incorrect user permission validation in Harbor <v2.9.5 and Harbor <v2.10.3 allows authenticated users to modify configurations.
- affected >= 2.8.1, < 2.8.6fixed 2.8.6
SQL-Injection in Harbor allows priviledge users to leak the task IDs
- affected >= 2.8.0, < 2.10.1fixed 2.10.1
Open Redirect in Harbor <=v2.8.4, <=v2.9.2, and <=v2.10.0 may redirect a user to a malicious site.
- affected < 1.10.17fixed 1.10.17
A timing condition in Harbor 2.6.x and below, Harbor 2.7.2 and below, Harbor 2.8.2 and below, and Harbor 1.10.17 and below allows an attacker with network access to create jobs/stop job tasks and retrieve job task information.
- affected >= 1.1.0, < 2.5.4fixed 2.5.4
An access control issue in Harbor v1.X.X to v2.5.3 allows attackers to access public and private image repositories without authentication. NOTE: the vendor's position is that this "is clearly described in the documentation as a feature."
- affected >= 2.0.0, < 2.0.5fixed 2.0.5
In Harbor 2.0 before 2.0.5 and 2.1.x before 2.1.2 the catalog’s registry API is exposed on an unauthenticated path.
- affected >= 1.9.0, < 2.0.3fixed 2.0.3
Harbor 1.9.* 1.10.* and 2.0.* allows Exposure of Sensitive Information to an Unauthorized Actor.
- affected < 2.0.1fixed 2.0.1
Harbor prior to 2.0.1 allows SSRF with this limitation: an attacker with the ability to edit projects can scan ports of hosts accessible on the Harbor server's intranet.