CVE-2022-46463· NVD / CVE Program· CNA mitre

An access control issue in Harbor v1.X.X to v2.5.3 allows attackers to access public and private image repositories without authentication.

Noroxi assessment

Priority: Monitor (action score 32/100)

Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
Probability of exploitation in the next 30 days: 6.2% (FIRST EPSS); higher than 93.4% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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."

HighCVSS 7.5 · v3.1—Proof of concept No fix recorded

Published: Jan 12, 2023
Updated: Jun 17, 2026
EPSS: 6.2% · 93th percentile
CWE: CWE-306

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 30 / 40 · 7.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 2 / 30 · 6.2%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
Proof of concept exists, no weaponized module
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
linuxfoundation	harbor	cpe:2.3:a:linuxfoundation:harbor

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

linuxfoundation harbor1.1.0 and later · up to 2.5.3 inclusive

Same product

linuxfoundation: all records

Other highest-scoring records for the same primary product.

CVE-2026-4404Use of hard coded credentials in GoHarbor Harbor
37Monitor
CVE-2019-19023Cloud Native Computing Foundation Harbor prior to 1.8.6 and 1.9.3 has a Privilege Escalation Vulnerability in the VMware Harbor Container Re
35Monitor
CVE-2017-17697The Ping() function in ui/api/target.go in Harbor through 1.3.0-rc4 has SSRF via the endpoint parameter to /api/targets/ping.
34Monitor

Published before and after this one in the same product

← EarlierCVE-2020-29662Feb 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.
21Monitor
← EarlierCVE-2019-19030Dec 26, 2022 · Cloud Native Computing Foundation Harbor before 1.10.3 and 2.x before 2.0.1 allows resource enumeration because unauthenticated API calls re
22Monitor
Later →CVE-2023-20902Nov 8, 2023 · Timing attack risk in Harbor
26Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

Proof-of-concept repository on GitHub ×3

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
Source	Kind	Date
Proof-of-concept repository on GitHub	stars:31	2023-01-17
Proof-of-concept repository on GitHub	stars:59	2023-03-21
Proof-of-concept repository on GitHub	stars:15	2024-12-23

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

PublishedJan 12, 2023
First PoCJan 17, 2023+4 d
TodayOct 18, 2026+1375 d

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: none
Availability: none

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: None
Availability impact: None

Weakness class (CWE)

CWE-306 · Missing Authentication for Critical Function

CVSS vector

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

nvd-primary

Root cause

A function added for development or support ships to production without authentication. It often relies on the assumption that it is “only reachable from the internal network.”

The bug in code

The whole CWE-306 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1// Added for the support team2app.post("/maintenance/reset", resetDevice);

Fixed

1if (config.maintenanceEnabled) {2  app.post(3    "/maintenance/reset",4    requireSession, requireRole("admin"), resetDevice5  );6}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

github.com/Vad1mo

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records