# CVE-2026-42018: JFrog Artifactory Improper Authentication

> Unauthenticated attackers can obtain internal anonymous tokens to access sensitive resources, even when anonymous access is disabled.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Yes, since 11 Sep 2026 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Aug 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-3q94-gprh-7pwm

## What is CVE-2026-42018?

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

### Official description

JFrog Artifactory could return an internal anonymous-user token to an unauthenticated caller when anonymous access is disabled, potentially exposing sensitive resources.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Jfrog Artifactory.

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

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

## Is CVE-2026-42018 being exploited?

Yes. Attackers have exploited CVE-2026-42018 in the wild since at least 11 Sep 2026.

Public exploit code:

- JFrog Artifactory - Anonymous Token Disclosure via Trailing Slash Auth Bypass (nuclei): http/cves/2026/CVE-2026-42018.yaml

## Other vulnerabilities in Jfrog Artifactory

- [CVE-2026-82329](https://insights.sbomify.com/CVE-2026-82329/): JFrog Artifactory Improper Authentication (critical 9.8, exploited in the wild)
- [CVE-2026-42016](https://insights.sbomify.com/CVE-2026-42016/): JFrog Artifactory Incorrect Authorization (high 8.1, 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-42018 and fix it if it is affected.

What it is: CVE-2026-42018 is a high-severity authentication bypass vulnerability in Jfrog Artifactory, published on 12 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-42018 in the wild since at least 11 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-42018/ (Markdown: https://insights.sbomify.com/CVE-2026-42018/index.md)
```

## Sources

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

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