NVD / CVE Program· CNA JFROG

CVE-2026-66384: Authenticated users may write data outside the intended Docker cache path

Noroxi assessment

Priority: Plan (action score 51/100)

CISA has confirmed exploitation in the wild (Aug 27, 2026). Remediation deadline for US federal agencies: Sep 10, 2026.
Probability of exploitation in the next 30 days: 0.66% (FIRST EPSS); higher than 51.8% of all records.
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
According to the record, no fixed version is available yet.

Add it to your regular patch cycle. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · CISA KEV · FIRST EPSS

An authenticated user may write data outside the intended Docker cache path under specific remote-repository conditions.

MediumCVSS 5.3 · v3.1KEVWeaponized No fix recorded

Path traversal

Published: Aug 12, 2026
Updated: Oct 24, 2026
EPSS: 0.6% · 51th percentile
CWE: CWE-22

Report tools

JSON

Action score

Plan

Add it to your regular patch cycle.

CVSS: 21 / 40 · 5.3 / 10
CISA KEV: 30 / 30 · Listed
EPSS: 0 / 30 · 0.6%

CISA SSVC decision

Exploitation: active
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · JFROG: 5.3; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Actively exploited in the wild

CISA added this to its Known Exploited Vulnerabilities catalog on Aug 27, 2026. That signals real attacks, not theory.

Remediation deadline for US federal agencies: Sep 10, 2026.

Get told when this record changes

In CISA KEV: exploitation in the wild confirmed
Weaponized exploit exists
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
jfrog	artifactory	cpe:2.3:a:jfrog:artifactory

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

jfrog artifactorybefore 7.146.35
jfrog artifactory7.161.0 and later · before 7.161.16

Versions reported by the vendor

Affected version ranges reported by the assigning authority (JFROG). Independent of NVD's CPE analysis and usually ahead of it.

jfrog artifactory
- before 7.146.35affected
- 7.161.0 and later · before 7.161.16affected

Same product

jfrog: all records

Other highest-scoring records for the same primary product.

CVE-2026-82329Potential authentication bypass leading to administrative access in ArtifactoryKEV
73This week
CVE-2026-42016Incorrect authorization validation of user token in JFrog Artifactory allows Privilege EscalationKEV
68This week
CVE-2026-42018Anonymous user token generation exposure in JFrog ArtifactoryKEV
63This week

Published before and after this one in the same product

← EarlierCVE-2026-65926Aug 12, 2026 · Private Release Bundle versions may be disclosed under specific configurations
12Monitor
← EarlierCVE-2026-66016Aug 12, 2026 · Rendered Artifactory Helm manifests may contain generated TLS private keys
26Monitor
Later →CVE-2026-68758Aug 12, 2026 · Authenticated users may access restricted Artifactory support information
26Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

Weaponized

A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.

Evidence

Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
Source	Kind	Date
Proof-of-concept repository on GitHub	stars:0	2026-08-28

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

PublishedAug 12, 2026
CISA KEVAug 27, 2026+14 d
First PoCAug 28, 2026+15 d
TodayNov 4, 2026+84 d

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Kostya KortchinskyOpenAIfinder

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-6592116 days apartPotential path traversal leading to unauthorized file writes
35Monitor
CVE-2026-663810 days apartRepository readers may access content outside configured upstream paths
21Monitor
CVE-2026-663820 days apartAuthenticated users may write files outside the intended Artifactory work directory
17Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

CVE-2026-8232916 days apartPotential authentication bypass leading to administrative access in ArtifactoryKEV
73This week
CVE-2026-420180 days apartAnonymous user token generation exposure in JFrog ArtifactoryKEV
63This week
CVE-2026-687600 days apartPotential remember-me authentication bypass in JFrog Artifactory
21Monitor

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
A low-privileged account is enough.
No user action is required.
Special conditions such as timing or configuration are required.

If successful

Confidentiality: none
Integrity: high · data or configuration can be modified
Availability: none

Attack vector: Network
Attack complexity: High
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: None
Integrity impact: High
Availability impact: None

Weakness class (CWE)

CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N

nvd-secondary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

The bug in code

The whole CWE-22 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const file = path.join(ROOT, req.query.name);
2res.sendFile(file);

Fixed

1const file = path.resolve(ROOT, req.query.name);
2if (!file.startsWith(ROOT + path.sep)) {
3  return res.sendStatus(400);
4}
5res.sendFile(file);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

docs.jfrog.com/releases/docs/artifactory-self-managed-releases

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records