CVE-2026-42018

HIGH(7.5)KEV

JFrog Artifactory Improper Authentication Vulnerability

Description

CVE-2026-42018 is a high-severity improper authentication vulnerability in JFrog Artifactory in which the server could return an internal anonymous-user token to an unauthenticated caller even when anonymous access has been explicitly disabled. An attacker who obtains this token can present it to the Artifactory API and read resources that the instance's configuration was supposed to keep private, making CVE-2026-42018 an unauthenticated information-disclosure vulnerability with a CVSS score of 7.5. Because Artifactory stores build artifacts, container images and package metadata for entire development organisations, exposure of a valid internal token undermines the security boundary that "anonymous access disabled" is meant to enforce. CISA has added this Artifactory vulnerability to the Known Exploited Vulnerabilities (KEV) catalog with a remediation deadline of 25 September 2026.

KEV Information

Vendor
JFrog
Product
Artifactory
Date Added
September 11, 2026
Due Date
September 25, 2026
Required Action
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.

CVSS Score

Vector String
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NOpen in Calculator
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
NONE
Availability Impact
NONE
Exploitability Score
3.9
Impact Score
3.6

CWEs

Affected Products

VendorProductVersion
jfrogartifactory< 7.111.20; >= 7.117.0, < 7.117.27; >= 7.125.0, < 7.125.19; >= 7.133.0, < 7.133.28; >= 7.146.0, < 7.146.8

References

Weakness Type

CWE-287: Improper Authentication

Improper authentication occurs when software does not adequately prove that an actor is who they claim to be, or when it grants an identity to a caller that should have none. In CVE-2026-42018 Artifactory hands an internal anonymous-user token to a caller who has not authenticated at all, effectively issuing a valid identity to an anonymous requester despite the configuration that disables anonymous access.

Learn more: CWE-287 — Improper Authentication

Impact Analysis

CVE-2026-42018 is remotely exploitable over the network with low attack complexity, no authentication and no user interaction, which means any party that can reach the Artifactory HTTP interface can attempt it. The consequence is high confidentiality impact, while integrity and availability are unaffected — the attacker gains read access to resources through the leaked internal token rather than the ability to modify or destroy them. In practice that can mean disclosure of private repositories, internal package names and versions, and any metadata reachable with the anonymous identity, which is valuable reconnaissance for a subsequent supply-chain attack. Rated CVSS 7.5 (High) with an EPSS score of roughly 0.9% (58th percentile), the statistical exploitation estimate is moderate, but CISA's KEV listing and vendor research on in-the-wild Artifactory exploitation mean this vulnerability is being used against real deployments and must be patched on schedule.

Exploit Maturity

CISA has confirmed active exploitation of CVE-2026-42018 by adding it to the Known Exploited Vulnerabilities catalog with a 25 September 2026 remediation deadline. Wiz has published research on in-the-wild exploitation of Artifactory vulnerabilities disclosed in the same round — see Wiz Research: Artifactory under attack — which documents that attackers are actively probing exposed Artifactory instances. The EPSS score of about 0.9% (58th percentile) understates the risk given the confirmed KEV status and the triviality of the request needed to trigger the flaw. The KEV ransomware flag is "Unknown", but exposed instances should be considered under opportunistic attack and patched without waiting for the deadline.

Remediation

  1. Follow the CISA KEV required action. Apply mitigations in accordance with JFrog's instructions, comply with CISA's BOD 26-04 "Prioritizing Security Updates Based on Risk" guidance and the "Forensics Triage Requirements", and discontinue use of the product if mitigations are unavailable. The KEV due date is 25 September 2026.
  2. Upgrade Artifactory to a fixed release for your branch. The fixed versions are 7.111.20 for releases below that line, 7.117.27 for the 7.117.x branch, 7.125.19 for 7.125.x, 7.133.28 for 7.133.x and 7.146.8 for 7.146.x; check the JFrog self-managed release notes for the exact build.
  3. Do not rely on "anonymous access disabled" as a compensating control. The defect specifically defeats that setting, so until the upgrade is complete restrict access to the Artifactory interface at the network layer — reverse proxy, VPN or firewall allowlisting of build agents and administrative networks.
  4. Review access logs for anonymous-token activity. Inspect Artifactory request and audit logs for API calls made with the internal anonymous identity, for unexpected repository listings or downloads from unfamiliar source addresses, and treat any private artifact retrieved that way as disclosed.
  5. Harden authentication long term by enforcing authenticated access with strong, centrally managed credentials, enabling multi-factor authentication for the Artifactory UI, applying rate limiting on the API surface, and periodically verifying from an unauthenticated client that no anonymous identity is issued.

Technical Details

CVE-2026-42018 is an improper authentication flaw (CWE-287) in JFrog Artifactory: a code path that produces the platform's internal anonymous-user token is reachable by a caller who has presented no credentials, and it emits that token even when the deployment's configuration has anonymous access turned off. The returned token is a genuine, server-issued credential, so downstream authorization decisions accept it as a legitimate identity and grant whatever access the anonymous principal retains internally — the authentication layer, not the authorization layer, is where the boundary breaks. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N confirms the attack is network-reachable, low-complexity, requires neither privileges nor user interaction, and yields high confidentiality impact only, with scope unchanged. Because exploitation is a matter of issuing an ordinary HTTP request against an exposed instance, no specialised tooling is needed and internet-facing Artifactory deployments are the primary exposure.

Frequently Asked Questions

Is CVE-2026-42018 being actively exploited?

Yes. CISA added CVE-2026-42018 to its Known Exploited Vulnerabilities catalog with a remediation due date of 25 September 2026, confirming exploitation in the wild. Vendor research published around the same disclosure documents active attacks against exposed JFrog Artifactory instances.

What products are affected by CVE-2026-42018?

The vulnerability affects JFrog Artifactory in versions before 7.111.20, in the 7.117.0 to 7.117.27 range, 7.125.0 to 7.125.19, 7.133.0 to 7.133.28 and 7.146.0 to 7.146.8. Each branch has its own fixed build, so the correct target version depends on the release line currently deployed.

How do I fix CVE-2026-42018?

Upgrade Artifactory to the fixed release for your branch — 7.111.20, 7.117.27, 7.125.19, 7.133.28 or 7.146.8 — as listed in JFrog's release notes and security advisories. Until the upgrade lands, restrict network access to the Artifactory interface, since the "anonymous access disabled" setting does not protect against this flaw.

How severe is CVE-2026-42018?

CVE-2026-42018 is rated High with a CVSS 3.1 base score of 7.5. It is exploitable over the network with low complexity and no authentication or user interaction, but its impact is limited to confidentiality — unauthorized read access via a leaked internal token — with no direct integrity or availability effect; the EPSS score is around the 58th percentile, yet confirmed KEV-listed exploitation makes prompt patching necessary.

CVSS Score

7.5
HIGH(7.5)

EPSS Score

EPSS Score9.98%
EPSS Percentile95.7%

Dates

PublishedAugust 12, 2026
Last ModifiedOctober 23, 2026
StatusAnalyzed
CVSS Versionv3.1

Need Help With Vulnerability Management?

Our security experts can help you prioritize and remediate vulnerabilities effectively.