# CVE-2026-82329: JFrog Artifactory Improper Authentication

> Unauthenticated attackers can bypass authentication to gain administrative privileges in JFrog Artifactory under default configurations.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 2 Sep 2026 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Aug 2026
- **Updated:** 3 Sep 2026
- **Also known as:** GHSA-c5pf-6p5j-gj87

## What is CVE-2026-82329?

CVE-2026-82329 is a critical authentication bypass vulnerability in Jfrog Artifactory, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

JFrog Artifactory contains an authentication weakness that, under default configuration, may allow an unauthenticated attacker with network access to obtain administrative privileges.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-82329?

It affects 1 product.


Products: Jfrog Artifactory.

## How do I fix CVE-2026-82329?

No fix has been published for CVE-2026-82329 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 5 Sep 2026.

## Is CVE-2026-82329 being exploited?

Yes. Attackers have exploited CVE-2026-82329 in the wild since at least 2 Sep 2026.

Public exploit code:

- CVE-2026-82329 JFrog Artifactory unauthenticated auth-bypass: reproducible Docker lab + URL-parameter validator PoC + patch-diff analysis (github_poc): https://github.com/dinosn/cve-2026-82329-jfrog-artifactory
- CVE-2026-82329 — JFrog Artifactory (self-hosted)  Auth Bypass (github_poc): https://github.com/ynsmroztas/CVE-2026-82329-JFrog-Artifactory-Auth-Bypass
- CVE-2026-82329 – JFrog Artifactory Auth Bypass Toolkit (CVSS 9.8) | Red/Blue Team suite for self-hosted Artifactory 7.x (111-161). 2 tools: Full Exploit (JWTforge, admin token, user create, mass scan, stealth, interactive menu, resistence, WAF bypass etc.), SafeChecker (version detect, audit, JSON report). 🦾 Use Ethically, Stay Legal :V (github_poc): https://github.com/tc4dy/CVE-2026-82329-PoC-Exploit
- CVE-2026-82329 — JFrog Artifactory Auth Bypass (github_poc): https://github.com/0xTerror/CVE-2026-82329-JFrog-Artifactory-
- CVE-2026-82329 — JFrog Artifactory unauthenticated authentication bypass ("phantom join key" -> forged service admin token) (github_poc): https://github.com/realalexandergeorgiev/artifactory-CVE-2026-82329-poc.py
- CVE-2026-82329 - Draft or TODO (github_poc): https://github.com/HORKimhab/CVE-2026-82329

## Other vulnerabilities in Jfrog Artifactory

- [CVE-2026-42016](https://insights.sbomify.com/CVE-2026-42016/): JFrog Artifactory Incorrect Authorization (high 8.1, exploited in the wild)
- [CVE-2026-42018](https://insights.sbomify.com/CVE-2026-42018/): JFrog Artifactory Improper Authentication (high 7.5, exploited in the wild)
- [CVE-2026-66384](https://insights.sbomify.com/CVE-2026-66384/): JFrog Artifactory Improper Limitation of a Pathname to a Restricted Directory (medium 5.3, exploited in the wild)
- [CVE-2019-17444](https://insights.sbomify.com/CVE-2019-17444/): JFrog Artifactory does not enforce default admin password change (critical 9.8)
- [CVE-2018-19971](https://insights.sbomify.com/CVE-2018-19971/): Missing authorization in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-82329 and fix it if it is affected.

What it is: CVE-2026-82329 is a critical authentication bypass vulnerability in Jfrog Artifactory, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2026-82329 in the wild since at least 2 Sep 2026.

Affected product: Jfrog Artifactory. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-82329/ (Markdown: https://insights.sbomify.com/CVE-2026-82329/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-82329
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-82329
- OSV: https://osv.dev/vulnerability/CVE-2026-82329

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-82329/
Summaries are generated and may contain mistakes; the official description above is the record.