← gociux.comall exploited CVEs

Exploited vulnerability · CISA KEV

Is CVE-2026-42016 exploited? Yes: in CISA KEV since 11 Sep 2026

Gociux · JFrog Artifactory · data: CISA KEV, CVE record, FIRST EPSS

Yes. CVE-2026-42016, JFrog Artifactory Incorrect Authorization Vulnerability, is being exploited in the wild. CISA added it to its Known Exploited Vulnerabilities catalog on 11 Sep 2026, 46 days after it was published. It affects JFrog Artifactory. If you run it, CISA's required action is: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

exploitedYesCISA KEV · 11 Sep 2026
ransomwareNot knownno confirmed use
EPSStop 5%very likely to be exploited
severity8.1CVSS 3.1 · high
US federal due25 Sep 2026BOD 22-01 deadline

What it is

JFrog Artifactory contains an incorrect authorization vulnerability that leads to a privilege escalation attack due to a validation check of the token signature/issuer and not the token’s scope.

VendorJFrog (4 exploited CVEs in KEV)
ProductArtifactory
VulnerabilityJFrog Artifactory Incorrect Authorization Vulnerability
WeaknessCWE-863
Published27 Jul 2026
Added to KEV11 Sep 2026
Reported by (CNA)JFROG

What to do

  1. Check whether you run it. Look for Artifactory in your asset inventory, including appliances and cloud images. Stack check lists every exploited JFrog CVE at once.
  2. Apply the fix. Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
  3. If you can't patch today, take the affected service off the internet or restrict who can reach it, and check its logs for signs of compromise since 27 Jul 2026.
  4. Get told next time. Email alerts when CISA adds a CVE for JFrog.

Other exploited CVEs in Artifactory

References

Questions

Is CVE-2026-42016 being exploited?

Yes. CISA added CVE-2026-42016 to the Known Exploited Vulnerabilities catalog on 11 Sep 2026, which means there is reliable evidence of exploitation in the wild.

Is CVE-2026-42016 used in ransomware attacks?

CISA does not list known ransomware use for it. That can change, and exploitation alone is reason to fix it first.

How do I fix CVE-2026-42016?

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. Check JFrog's advisory for the fixed versions, and if you can't patch quickly, restrict access to the affected Artifactory and watch it for signs of compromise.

Sources: CISA KEV (exploitation, ransomware use, required action, due date), the CVE record (publication date, CVSS, CNA), NVD and FIRST EPSS (live score). More: all KEV additions in September 2026 · JFrog scorecard · act-now radar.

Running JFrog in a regulated environment?

We check exposure across your estate, patch or mitigate with your team, and set up detection for what attackers do after exploiting it.

Get in touch →