Critical JFrog Artifactory Flaw CVE-2026-82329 Actively Exploited to Forge Admin Tokens in Self-Managed Deployments
A critical vulnerability tracked as CVE-2026-82329 in JFrog Artifactory is being actively exploited by attackers to issue administrator tokens without any authentication on self-managed installations that use default settings.
The flaw allows an unauthenticated attacker with network access to the instance to bypass authentication entirely and obtain full administrative privileges. From this position the intruder can enumerate users, groups, and credential sets, inspect sensitive configurations, and gain visibility into federated topologies.
Attackers can also read stored artifacts and alter security settings. This combination is particularly dangerous in organizations that rely on Artifactory as the central component of their software build and publication lifecycle.
The most damaging scenario occurs when the repository automatically supplies artifacts to CI/CD tools and deployment pipelines. By replacing an internal package, container image, or dependency that the organization trusts, the attacker can propagate the change downstream from integration runners all the way to production environments, creating a classic supply-chain compromise with a single point of entry affecting multiple systems.
JFrog Cloud was already protected against the issue. Self-managed deployments must be updated to one of the following patched versions depending on the release branch: 7.111.21, 7.117.28, 7.125.20, 7.133.29, 7.146.38, or 7.161.20.
Applying the patch alone is insufficient if tokens have already been issued, because token validity, expiration, and revocation function independently of the binary update. Recommended actions include prioritizing internet-exposed instances, restricting network access, revoking and reissuing administrator tokens, reviewing expiration policies, and rotating credentials tied to pipelines and systems that authenticate against the repository.
Security teams should examine audit logs for anomalous token generation, mass user and group enumeration, configuration changes, and unusual administrative API access. Environments that remained exposed during the vulnerable window should be treated as potentially compromised, which includes validating the integrity of all artifacts published in that period and checking for unauthorized substitutions.
Additional hardening measures involve pinning images to immutable digests and verifying signatures and provenance at deployment time. Investigations should also extend to connected systems such as CI runners, deployment managers, and production servers to rule out persistence or malicious modifications.
Related articles
Malicious Code Injected into LiteLLM Open Source AI Package via Supply Chain Attack
The open-source generative AI tool LiteLLM had malicious code inserted into its official distribution packages, enabling credential theft and remote code execution. The compromise affected version 1.107.0 released on October 21, 2026, and was delivered through legitimate channels in a classic software supply chain attack. Seven malicious wheel files were uploaded to PyPI, while official container images on Docker Hub and GitHub Container Registry were also tainted. Security firm JFrog discovered that the malware steals a wide range of secrets including cloud credentials, SSH private keys, browser-stored passwords, development tokens, and AI service API keys from LiteLLM's database. The code also supports execution of externally fetched payloads and abuses Python's startup mechanisms to run even when the application itself is not loaded. This marks the second supply chain incident involving the project in 2026, following a separate event in March.
GhostAction Campaign Compromises 790 GitHub Repositories via Malicious Workflows
Researchers from OpenSourceMalware have identified 790 publicly accessible GitHub repositories containing malicious workflows planted by the GhostAction campaign as of October 9. The campaign abuses trusted maintainer accounts to inject workflows that automatically exfiltrate secrets including AWS access keys and tokens for GitHub, GitLab, Google, Slack, SendGrid, OpenAI, Anthropic, and OpenRouter. Earlier counts by GitGuardian recorded 772 repositories between August 31 and September 30, though the datasets differ and are not cumulative. A separate wave on October 8 impacted 346 repositories linked to two maintainer accounts, including a project belonging to Uber. The malicious workflow runs on code pushes or manual triggers, scans repository files and full Git history for credentials, and sends findings in plaintext to attacker infrastructure. Removing the workflow file does not mitigate exposure, as successful executions already leak credentials and old commits may still contain secrets.
SberTech Launches Platform V Orchestrator for Security Services to Scan Software Before Corporate Deployment
SberTech has announced the launch of a new direction focused on analyzing the security of software prior to its integration into corporate infrastructures. The initiative is built around the company's own Laboratory for Software Verification and the technological platform Platform V Orchestrator for Security Services. This platform combines components for working with both built-in and external analysis tools, enabling checks of digital artifacts, control over software composition and changes, and detection of vulnerabilities, hidden threats, and defects in source code and repositories. SberTech aims to replace fragmented checks and manual result processing with a single managed process, allowing scaled verification without proportional team growth. The move responds to the adoption of hundreds of products from various vendors, widespread use of open-source components, and rising attacks on software supply chains. Primary customers include banks, industrial enterprises, telecom operators, energy companies, and the public sector. The solution is offered as a standalone product that supports on-premises deployment and operation in isolated environments such as private clouds and dedicated data processing contours.
NEC Subcontractor Suffers Cyber Attack Leading to Customer System Disruptions and Personal Data Leak
NEC disclosed that a subcontractor handling system development and maintenance was compromised in a cyber attack during late September 2026. Attackers stole legitimate account credentials and used them to access multiple customer environments from the subcontractor's systems. The intrusion resulted in server files being encrypted, rendering customer systems inoperable. Additional files containing personal information and system details were exfiltrated from a shared cloud storage platform used for coordination between NEC, the subcontractor, and customers. Affected customers have been notified individually, with further details on compromised personal data to be provided as they become available. The incident highlights risks associated with third-party vendor access in IT supply chains.