JFrog Artifactory could return an internal anonymous-user token to an unauthenticated caller when anonymous…

CVE-2026-42018 is an authentication bypass in JFrog Artifactory's /api/v1/aws/token endpoint. A trailing-slash mismatch in the request filter causes Artifactory to fall back to an anonymous security context and mint a valid JWT for the internal anonymous user — even when anonymous access has been explicitly disabled. This affects both Artifactory OSS and Enterprise editions prior to version 7.146.8. The flaw was discovered by NetSPI and is chainable with CVE-2026-69107 (stash search path traversal + arbitrary export), which together allow an unauthenticated attacker to read restricted artifact bytes and write them to attacker-chosen filesystem locations.

JFrog's HIGH / 7.5 rating is *defensible but slightly conservative*. The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) accurately captures the unauthenticated remote access and high confidentiality impact. However, it doesn't account for two real-world amplifiers: (1) Artifactory is canonically a supply-chain component — every artifact your CI/CD pipeline publishes or consumes lives here, and (2) the anonymous JWT enables the chain with CVE-2026-69107, turning a token leak into file-system-level exfiltration. The vendor score treats this as a standalone information-disclosure bug; in practice, it's the entry point to a supply-chain read-out chain. We nudge it to 7.8 to reflect the role multiplier while acknowledging that most Artifactory instances sit behind corporate networks, limiting the unauthenticated attack surface.

Why this verdict

• Unauthenticated remote entry point: AV:N/PR:N/UI:N means any network-adjacent attacker can obtain the JWT with a single HTTP request — no credentials, no social engineering, no user interaction required.
• Role multiplier — supply-chain artifact store: Artifactory is not a line-of-business app; it is the canonical CI/CD artifact repository. Over 40% market share in universal artifact management. ≥10% of installs *are* the high-value role by definition. A read-out of all artifacts = proprietary code, embedded secrets, Docker images, Helm charts. The blast radius is supply-chain-scale, flooring the verdict at HIGH.
• Chain amplifier with CVE-2026-69107: The anonymous JWT is the entry point to a documented chain that escalates from token leak to filesystem-level path-traversal exfiltration. Both CVEs are fixed in the same release (7.146.8), meaning unpatched instances are vulnerable to the full chain.
• Friction discount — network exposure: The majority (~72%) of Artifactory deployments are JFrog-managed SaaS, which are patched by JFrog and not in scope. Self-hosted instances are typically behind corporate firewalls/VPNs. This limits the unauthenticated attack surface but does not eliminate it — remote CI runners, developer VPN access, and post-initial-access scenarios all provide network reachability.
• No active exploitation or PoC (partial friction): EPSS at 0.3%, no KEV listing, no public PoC. This prevents an upgrade to CRITICAL but does not override the role-multiplier floor.

Why not higher?

CRITICAL would require either active exploitation (KEV listing, confirmed campaigns) or a chain that delivers RCE/supply-chain *write* access. CVE-2026-42018 alone delivers confidentiality impact only (C:H/I:N/A:N). The full chain with CVE-2026-69107 enables read-exfiltration and filesystem writes, but the write target is limited to the Artifactory host's filesystem, not arbitrary code execution in the build pipeline. The 72% SaaS deployment share also narrows the self-managed exposure population, and no public PoC exists to lower the exploitation barrier.

Why not lower?

MEDIUM would require the blast radius to be tenant-scoped or the attack surface to be negligible. Artifactory is a supply-chain component by definition — even if only 28% of deployments are self-managed, that represents ~1,400+ large enterprises. The unauthenticated entry point (PR:N) means no prior compromise is needed, just network reachability. The July 2026 OpenAI/Hugging Face incident proved that Artifactory zero-days are actively sought and exploited, even if this specific CVE was not involved.

1. Block trailing-slash variants on /api/v1/aws/token at WAF/reverse proxy — Add a WAF or reverse-proxy rule (nginx, HAProxy, F5, Cloudflare) that rejects or normalizes requests to /api/v1/aws/token/ with a trailing slash. This directly blocks the bypass mechanism. Deploy within 30 days per the noisgate mitigation SLA for HIGH.
2. Audit and strip anonymous user permissions — Even if anonymous access is disabled, verify that the internal anonymous user principal has zero repository permissions. In Artifactory Admin → Security → Permissions, ensure no permission target includes the anonymous user or the readers group (which often includes anonymous). This limits the blast radius of any minted anonymous JWT to zero. Deploy within 30 days.
3. Restrict network access to Artifactory — Ensure Artifactory is not exposed to the public internet. Place it behind VPN, zero-trust network access (ZTNA), or IP allowlisting. If remote CI runners need access, use a dedicated service mesh or private link. This eliminates the unauthenticated remote attack vector for external adversaries.
4. Enable and monitor audit logging for anonymous principal activity — Configure Artifactory to log all API calls and set up SIEM alerts for any activity from the anonymous principal when anonymous access is disabled. This is a direct anomaly indicator of exploitation.
5. Upgrade to Artifactory 7.146.8 or later — The definitive fix. This patches both CVE-2026-42018 and CVE-2026-69107. Apply within the 180-day noisgate remediation SLA for HIGH, but prioritize earlier given the supply-chain role.

Run this script on any host with network access to your Artifactory instance. Usage: bash check_cve_2026_42018.sh https://your-artifactory.example.com. No special privileges required — it makes a single unauthenticated HTTP request.

#!/usr/bin/env bash
# check_cve_2026_42018.sh — Detect CVE-2026-42018 (JFrog Artifactory anonymous JWT bypass)
# Usage: bash check_cve_2026_42018.sh <ARTIFACTORY_BASE_URL>
# Exit codes: 0 = PATCHED, 1 = VULNERABLE, 2 = UNKNOWN

set -euo pipefail

if [[ $# -lt 1 ]]; then
  echo "Usage: $0 <ARTIFACTORY_BASE_URL>"
  echo "Example: $0 https://artifactory.corp.example.com"
  exit 2
fi

BASE_URL="${1%/}"
ENDPOINT="${BASE_URL}/api/v1/aws/token/"

echo "[*] Testing CVE-2026-42018 against: ${BASE_URL}"
echo "[*] Sending trailing-slash request to: ${ENDPOINT}"

# Make the request and capture HTTP status + body
HTTP_RESPONSE=$(curl -s -o /tmp/cve_2026_42018_resp.txt -w "%{http_code}" \
  --max-time 10 \
  -H "Accept: application/json" \
  "${ENDPOINT}" 2>/dev/null || echo "000")

RESP_BODY=$(cat /tmp/cve_2026_42018_resp.txt 2>/dev/null || echo "")
rm -f /tmp/cve_2026_42018_resp.txt

echo "[*] HTTP status: ${HTTP_RESPONSE}"

if [[ "${HTTP_RESPONSE}" == "000" ]]; then
  echo "UNKNOWN — Could not connect to ${BASE_URL}. Verify URL and network access."
  exit 2
fi

# Check if a JWT token was returned in the response
if echo "${RESP_BODY}" | grep -qiE '("token"\s*:|"access_token"\s*:|eyJ[A-Za-z0-9_-]+\.)'; then
  echo "VULNERABLE — Artifactory returned a token via the trailing-slash bypass."
  echo "[!] Anonymous JWT minted despite anonymous access being disabled."
  echo "[!] Upgrade to Artifactory >= 7.146.8 immediately."
  exit 1
fi

if [[ "${HTTP_RESPONSE}" == "401" || "${HTTP_RESPONSE}" == "403" || "${HTTP_RESPONSE}" == "404" ]]; then
  echo "PATCHED — Endpoint returned ${HTTP_RESPONSE}. No anonymous token minted."
  exit 0
fi

if [[ "${HTTP_RESPONSE}" == "200" ]]; then
  # 200 but no token pattern — might be a different response format
  echo "UNKNOWN — Got 200 but no token pattern detected. Manual review recommended."
  echo "Response preview: $(echo "${RESP_BODY}" | head -c 200)"
  exit 2
fi

echo "UNKNOWN — Unexpected HTTP ${HTTP_RESPONSE}. Manual review recommended."
exit 2

Sources

1. NetSPI Research — Stealing the Artifact (Full Chain Analysis)
2. JFrog Security Advisories
3. JFrog Fixed Security Vulnerabilities
4. JFrog Artifactory Market Share — 6sense
5. PentesterLab — Research Worth Reading Week 33 2026
6. The Hacker News — JFrog Artifactory Zero-Days and Hugging Face Breach
7. SecurityWeek — JFrog Zero-Days in OpenAI-Hugging Face Hack