CVE-2026-82329: Potential authentication bypass leading to administrative access in Artifactory
Noroxi assessment
Priority: This week (action score 73/100)
- CISA has confirmed exploitation in the wild (Sep 2, 2026). Remediation deadline for US federal agencies: Sep 5, 2026.
- A ready-made attack module is public (Nuclei); exploiting it takes no special expertise.
- Probability of exploitation in the next 30 days: 14.3% (FIRST EPSS); higher than 96.6% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- According to the record, no fixed version is available yet.
Don’t wait for the next maintenance window. Until a fix is released, restrict access to the affected component and 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
JFrog Artifactory contains an authentication weakness that, under default configuration, may allow an unauthenticated attacker with network access to obtain administrative privileges.
- Published
- Aug 28, 2026
- Updated
- Sep 3, 2026
- EPSS
- 14.3% · 96th percentile
- CWE
- CWE-287
Report tools
Action score
73
This week
Don’t wait for the next maintenance window.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 30 / 30 · Listed
- EPSS
- 4 / 30 · 14.3%
CISA SSVC decision
- Exploitation
- active
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · JFROG
- 9.8
- 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 Sep 2, 2026. That signals real attacks, not theory.
Remediation deadline for US federal agencies: Sep 5, 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.
Is your version affected? Check itNoroxi 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 helpAffected 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 artifactory7.111.4 and later · before 7.111.21
- jfrog artifactory7.117.0 and later · before 7.117.28
- jfrog artifactory7.125.0 and later · before 7.125.20
- jfrog artifactory7.133.0 and later · before 7.133.29
- jfrog artifactory7.146.0 and later · before 7.146.38
- jfrog artifactory7.161.0 and later · before 7.161.20
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.111.21affected
- 7.117.0 and later · before 7.117.28affected
- 7.125.0 and later · before 7.125.20affected
- 7.133.0 and later · before 7.133.29affected
- 7.146.0 and later · before 7.146.38affected
- 7.161.0 and later · before 7.161.20affected
Same product
jfrog: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-42016Incorrect authorization validation of user token in JFrog Artifactory allows Privilege EscalationKEV68This week
- CVE-2026-42018Anonymous user token generation exposure in JFrog ArtifactoryKEV63This week
- CVE-2019-17444JFrog Artifactory does not enforce default admin password change60This week
Published before and after this one in the same product
- ← EarlierCVE-2026-70551Aug 25, 2026 · Server-Side Request Forgery Via VCS remote download in JFrog Artifactory34Monitor
- ← EarlierCVE-2026-70548Aug 25, 2026 · SSRF In CocoaPods Via JFrog Artifactory External Dependency14Monitor
- ← EarlierCVE-2026-70550Aug 25, 2026 · Potential unauthorized access to private Composer repository metadata in JFrog Artifactory26Monitor
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
- Nuclei detection template ×1
- Proof-of-concept repository on GitHub ×8
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.
| Source | Kind | Date |
|---|---|---|
| Nuclei detection template | Nuclei template CVE-2026-82329 | — |
| Proof-of-concept repository on GitHub | stars:0 | 2026-09-01 |
| Proof-of-concept repository on GitHub | stars:12 | 2026-09-01 |
| Proof-of-concept repository on GitHub | stars:1 | 2026-09-02 |
| Proof-of-concept repository on GitHub | stars:6 | 2026-09-02 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-09-03 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-09-04 |
| Proof-of-concept repository on GitHub | stars:3 | 2026-09-07 |
| Proof-of-concept repository on GitHub | stars:4 | 2026-09-15 |
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.
- Published
- First PoC+3 d
- CISA KEV+4 d
- TodayNov 11, 2026+75 d
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 researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-4201816 days apartAnonymous user token generation exposure in JFrog ArtifactoryKEV63This week
- CVE-2026-6601432 days apartPotential authentication bypass leading to privilege escalation in Artifactory35Monitor
- CVE-2026-6876016 days apartPotential remember-me authentication bypass in JFrog Artifactory21Monitor
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-6638416 days apartAuthenticated users may write data outside the intended Docker cache pathKEV51Plan
- CVE-2026-705513 days apartServer-Side Request Forgery Via VCS remote download in JFrog Artifactory34Monitor
- CVE-2026-6638116 days apartRepository readers may access content outside configured upstream paths21Monitor
- CVE-2026-705483 days apartSSRF In CocoaPods Via JFrog Artifactory External Dependency14Monitor
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.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-287 · Improper AuthenticationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Root cause
Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.
The bug in code
The whole CWE-287 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use("/admin", requireSession, adminRouter);
// Route added later skips the middleware
app.post("/admin-api/config", updateConfig);Fixed
const admin = express.Router();
admin.use(requireSession, requireRole("admin"));
admin.post("/config", updateConfig);
app.use("/admin", admin);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)
- Authentication AbuseCAPEC-114Medium
- Authentication BypassCAPEC-115Medium
- Identity SpoofingCAPEC-151likelihood: Medium · Medium
- Fake the Source of DataCAPEC-194Medium
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- Utilizing REST's Trust in the System Resource to Obtain Sensitive DataCAPEC-57likelihood: Medium · Very High
- Session HijackingCAPEC-593likelihood: High · Very High
- Token ImpersonationCAPEC-633Medium
ATT&CK techniques
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.