# CVE-2026-42017: Privilege escalation via JFrog Worker event token exposure

> A lower-privileged user can obtain privileged authorization tokens via an event-handling flaw, enabling privilege escalation in JFrog Artifactory.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jul 2026
- **Updated:** 27 Jul 2026
- **Also known as:** GHSA-g554-2364-r9j6

## What is CVE-2026-42017?

CVE-2026-42017 is a high-severity vulnerability in Jfrog Artifactory, published on 27 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An event-handling weakness in JFrog Artifactory could expose privileged authorization material to a lower-privileged user under specific conditions.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Jfrog Artifactory.

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

No fix has been published for CVE-2026-42017 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-42017 being exploited?

There is no known exploitation of CVE-2026-42017 in the wild and no public exploit code.

## 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-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)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-42017 is a high-severity vulnerability in Jfrog Artifactory, published on 27 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-42017 in the wild and no public exploit code.

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-42017/ (Markdown: https://insights.sbomify.com/CVE-2026-42017/index.md)
```

## Sources

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

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