Artifactory grants admin, exploited (CVE-2026-82329) [PoC]
CVE-2026-82329
CVE-2026-82329: unauthenticated attacker gains admin in JFrog Artifactory default configs (CVSS 9.8), actively exploited. Patch to 7.71.14 or 6.23.55 now.
Actively exploited in the wild - CVE-2026-82329 is a critical authentication weakness in JFrog Artifactory versions before 7.71.14 and 6.23.55 that grants unauthenticated network attackers full administrative privileges under default configuration. Patched in the versions above; update immediately if you have not done so.
Overview
CVE-2026-82329 resides in the authentication mechanism of JFrog Artifactory, a widely used binary repository manager. The flaw stems from how the product handles session validation under its default configuration. An attacker who can reach the Artifactory web interface or API over the network does not need valid credentials, user interaction, or any special access to exploit this weakness. The attack complexity is low, meaning the exploit path is straightforward and does not require advanced conditions to align.
The consequence is severe: a successful exploit completely bypasses authentication and grants the attacker administrator-level control over the entire Artifactory instance. Because the vulnerability carries a CVSS score of 9.8, its impact on confidentiality, integrity, and availability is rated as total. An attacker with admin rights can access, modify, or delete any stored artifacts, including source code, binaries, and container images. They can also tamper with build pipelines that depend on Artifactory, potentially injecting malicious code into downstream software supply chains.
Confirmation from CISA’s Known Exploited Vulnerabilities (KEV) catalog indicates this is not a theoretical risk. Threat actors are actively using this flaw in real-world attacks. The EPSS model estimates a 1.2% probability of exploitation within the next 30 days, a signal that scanning and opportunistic exploitation are already underway.
Affected Systems
The vulnerability affects JFrog Artifactory instances running versions prior to 7.71.14 (7.x line) and versions prior to 6.23.55 (6.x line). Any self-hosted deployment running these older builds is exposed if the service is reachable from untrusted networks.
Remediation and Mitigation
Immediate action is required given the active exploitation status.
- Patch now: Upgrade JFrog Artifactory to version 7.71.14, 6.23.55, or any newer release. These versions contain the fix for CVE-2026-82329.
- Restrict network access: If an immediate upgrade is not possible, place Artifactory behind a firewall or VPN. Do not expose the admin interface or API to the public internet.
- Audit for compromise: Review user accounts and admin logs for unauthorized changes. Assume compromise if the system was internet-facing before patching, and rotate all credentials stored within Artifactory.
- Monitor outbound traffic: Watch for unusual data exfiltration patterns from the Artifactory host.
For ongoing tracking, consult cybersecurity news at security news and data breach reports at breach reports.
Security Insight
The default-configuration nature of this flaw stands out. Many authentication bypasses require a specific setup mistake, but this one ships in the baseline install. That pattern, where the vendor’s default is insecure, forces organizations to scrutinize out-of-the-box settings rather than assume safety. Recent attacks on repository managers, such as those targeting npm and PyPI ecosystems, show that software supply chain infrastructure remains a prime target. This vulnerability reinforces that binary repositories are not just storage; they are trust boundaries that deserve the same scrutiny as production application servers.
Further Reading
Never miss a critical vulnerability
Get real-time security alerts delivered to your preferred platform.
Public PoC References
Unverified third-party code
These repositories are publicly listed on GitHub and have not been audited by Yazoul Security. They may contain malware, backdoors, destructive payloads, or operational security risks (telemetry, exfiltration). Treat them as hostile binaries. Inspect source before execution. Run only in isolated, disposable lab environments (offline VM, no credentials, no production data).
Authorized use only. This information is provided for defensive research, detection engineering, and patch validation. Using exploit code against systems you do not own or do not have explicit written permission to test is illegal in most jurisdictions and violates Yazoul's terms of use.
| Repository | Stars |
|---|---|
| HORKimhab/CVE-2026-82329 CVE-2026-82329 - Draft or TODO | ★ 0 |
Showing 1 of 1 known references. Source: nomi-sec/PoC-in-GitHub.
Nuclei Detection Templates
Detection template available — your exposure is being scanned
The templates below are YAML signatures for the Nuclei scanner from ProjectDiscovery. They are not exploit code — they are detection rules that confirm whether a target is vulnerable. The presence of a Nuclei template means every bug bounty hunter, AppSec team, red team, and reconnaissance pipeline on the public internet is actively probing for this CVE.
Assume your exposed instances have already been touched. Patch immediately even if no exploitation is observed yet — fingerprinting precedes exploitation by days at most.
| Template | Source |
|---|---|
CVE-2026-82329.yaml | View YAML |
1 Nuclei template indexed for this CVE. Source: projectdiscovery/nuclei-templates.
Related Advisories
An authentication issue was addressed with improved state management. This issue is fixed in macOS Sequoia 15.7.9, macOS Sonoma 14.8.9, macOS Tahoe 26.6.1. An attacker on the network may be able to au...
An authentication bypass vulnerability in the Check Point SmartConsole login process allows an unauthenticated remote attacker to obtain an application login token and use it to authenticate with full...
A logic flow weakness in Remote Access and Mobile Access certificate validation in deprecated IKEv1 key exchange allows an unauthenticated remote attacker to bypass user authentication and establish a...
May 2026: This security advisory provides the details and fix information for a vulnerability that was discovered and fixed after the was disclosed in February 2026. This new advisory is for a new vu...