VYPR

Go modules package

github.com/goharbor/harbor

pkg:golang/github.com/goharbor/harbor

Vulnerabilities (22)

  • CVE-2026-4404Mar 23, 2026
    affected <= 2.15.0

    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-30086MedJul 25, 2025
    affected >= 2.13.0, < 2.13.1fixed 2.13.1

    CNCF Harbor 2.13.x before 2.13.1 and 2.12.x before 2.12.4 allows information disclosure by administrators who can exploit an ORM Leak present in the /api/v2.0/users endpoint to leak users' password hash and salt values. The q URL parameter allows a user to filter users by any col

  • CVE-2025-32019MedJul 23, 2025
    affected >= 2.12.0-rc1, < 2.12.4-rc1fixed 2.12.4-rc1

    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-31668Nov 14, 2024
    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

  • CVE-2022-31667Nov 14, 2024
    affected >= 1.0.0, < 1.10.13fixed 1.10.13

    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-31669Nov 14, 2024
    affected >= 1.0.0, < 1.10.13fixed 1.10.13

    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-31670Nov 14, 2024
    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

  • CVE-2022-31671Nov 14, 2024
    affected >= 1.0.0, < 1.10.13fixed 1.10.13

    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-31666Nov 14, 2024
    affected >= 1.0.0, < 1.10.13fixed 1.10.13

    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-22278Aug 2, 2024
    affected < 2.9.5fixed 2.9.5

    Incorrect user permission validation in Harbor <v2.9.5 and Harbor <v2.10.3 allows authenticated users to modify configurations.

  • CVE-2024-22261Jun 10, 2024
    affected < 2.8.6fixed 2.8.6

    SQL-Injection in Harbor allows priviledge users to leak the task IDs

  • CVE-2024-22244Jun 10, 2024
    affected < 2.8.5fixed 2.8.5

    Open Redirect in Harbor  <=v2.8.4, <=v2.9.2, and <=v2.10.0 may redirect a user to a malicious site.

  • CVE-2023-20902Nov 9, 2023
    affected < 1.10.18fixed 1.10.18

    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-2019-19030Dec 26, 2022
    affected >= 1.7.0, < 1.10.3fixed 1.10.3

    Cloud Native Computing Foundation Harbor before 1.10.3 and 2.x before 2.0.1 allows resource enumeration because unauthenticated API calls reveal (via the HTTP status code) whether a resource exists.

  • CVE-2020-29662Feb 2, 2021
    affected < 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.

  • CVE-2020-13794Sep 29, 2020
    affected < 2.0.3fixed 2.0.3

    Harbor 1.9.* 1.10.* and 2.0.* allows Exposure of Sensitive Information to an Unauthorized Actor.

  • CVE-2020-13788Jul 15, 2020
    affected >= 1.8.0, < 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.

  • CVE-2019-19023Mar 20, 2020
    affected >= 1.7.0, < 1.8.6fixed 1.8.6

    Cloud Native Computing Foundation Harbor prior to 1.8.6 and 1.9.3 has a Privilege Escalation Vulnerability in the VMware Harbor Container Registry for the Pivotal Platform.

  • CVE-2019-19029Mar 20, 2020
    affected >= 1.7.0, < 1.8.6fixed 1.8.6

    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.

  • CVE-2019-19026Mar 20, 2020
    affected >= 1.7.0, < 1.8.6fixed 1.8.6

    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.

Page 1 of 2