JFrog Artifactory KEV flaws: token scope matters more than the patch

CISA added two JFrog Artifactory vulnerabilities to its Known Exploited Vulnerabilities catalog on September 11, 2026, giving federal agencies until September 25 to remediate under Binding Operational Directive 26-04. Security researchers at Wiz say attackers have already chained the two flaws in the wild to escalate from an anonymous connection to full administrative access on self-hosted Artifactory instances.

What the two CVEs do

CVE-2026-42018 is an improper-authentication flaw that can cause Artifactory to hand an internal anonymous-user token to an unauthenticated request, even when anonymous access is disabled. CVE-2026-42016, rated CVSS 8.1, is a privilege-escalation issue: Artifactory validates a token's signature and issuer but not its scope, so a token meant to cover a narrow action can be reused for more than it was intended to allow.

Wiz reports attackers have used the combination since at least mid-August 2026 to create persistent admin accounts, install malicious plugins for code execution, and pull configuration data and cluster keys. At disclosure, Wiz measured roughly two-thirds of organizations running Artifactory as still holding at least one vulnerable instance.

Why "signed and valid" is not the same as "scoped correctly"

For EU MSPs auditing customer instances, the operative question is not whether a token's signature checks out — it usually does — but whether the platform separately enforces which tenant, repository, path and verb that token may touch. Signature and issuer validation answer "who issued this?" and "was it tampered with?" They do not answer "what is this allowed to do?" Ask any vendor, JFrog included, to demonstrate scope enforcement and denial logging with non-production evidence before treating a patched version number as the end of the review.

What to re-check after patching

• Update to a fixed Artifactory release — 7.161.20, 7.146.38, 7.133.29, 7.125.20, 7.117.28 or 7.111.21 — matched to the branch in use.
• Re-audit anonymous-access settings and repository permissions, not just the version string.
• Review service-account token audiences and revoke anything issued before the patch.
• Confirm cross-tenant boundaries hold under the same scope test used to validate the fix.

The patch closes the specific bypass; it does not retroactively narrow tokens that were already over-scoped. Treat credential rotation and scope review as part of remediation, not an optional follow-up.

Sources: CISA KEV catalog, JFrog security advisories, SecurityWeek.