Skip to main content
VulnerabilityPublished Updated

CVE-2026-42016: jfrog artifactory · Incorrect Authorization

Affects jfrog artifactorySource CVE Database V5

0

Exploited in the wild · KEV due 25 Sep 2026 · 8% EPSS : upgrade to 7.133.11 now.

Data as of 27 Oct 2026, 05:11 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
KEV deadline
 US federal agencies must patch by this date; a sensible deadline for everyone else. Other KEV due dates
EPSS
8.6% chance of exploitation in 30 days – higher than 95% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 7.133.11
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 27 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: evidence found.

    Listed in CISA KEV 46 days after disclosure

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by JFrog

    , 95 days before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. In Threat Radar

    record ingested

    , 1 hour after disclosure

  4. , 46 days after disclosure

  5. KEV remediation due

    US federal deadline

    , 60 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade jfrog artifactory to 7.133.11.

Affected software

ProductAffectedFixed in
jfrogartifactoryAffected
  • <7.133.11
Fixed in
  • 7.133.11

Description

JFrog Artifactory (Self Hosted) versions before 7.133.11 are vulnerable to a privilege escalation attack due to a validation check of the token signature/issuer and not the token’s scope.

References

Community reviews

Loading reviews…