MeridianMeridian

Vendor Responsibility in Open Source: Licensing Obligations Exposed by Sonatype Nexus Changes

The article examines how vendors building products on copyleft open source projects like Nexus Repository OSS inherit significant legal and security responsibilities under licenses such as EPL 1.0. Sonatype's February 2025 shift from regular OSS binary releases to a limited Community Edition forces downstream vendors to handle their own builds, patch porting, and compliance disclosures. This change highlights the second part of copyleft licenses that outlines obligations for distributors, including revealing modifications and assuming liability for the final product. Security implications arise because critical vulnerabilities in the upstream project must now be tracked and patched by the vendor, with delays creating measurable supply chain risks. The piece provides a practical checklist for buyers to assess licensing hygiene, SBOM availability, and vulnerability response times in any open source-based solution.

HabrTranslated from Russian

Read at source

The original open source project continues to receive updates on GitHub under EPL 1.0, yet ready binary distributions have ceased. Vendors who previously layered their enhancements on top of official Sonatype builds must now compile from source and maintain their own fork.

CodeScoring analysts note that this situation is not unique to Nexus Repository. Any product built on a copyleft-licensed component carries the same duties: disclose changes to the original code, clearly separate proprietary modules from modified upstream files, and accept full commercial liability because the original authors disclaim all warranties.

Under EPL 1.0, weak copyleft applies only to modified files. Vendors may distribute the combined binary under a single commercial license provided they identify the EPL-covered portions, supply access instructions for corresponding source code, and ensure that their own additions are not derivative works of the upstream project.

Security consequences are direct. Sonatype has historically addressed critical vulnerabilities in Nexus Repository within days of disclosure. Once a vendor maintains a divergent fork, the time between upstream advisory and patched customer release becomes a measurable supply-chain metric. A one-year lag in the base version already signals missing or manual patch processes.

The recommended buyer checklist includes confirming the exact upstream version in use, locating published modifications required by the license, verifying an SBOM for the final product, and obtaining documented vulnerability response timelines. Answers such as “intellectual property” to source disclosure requests contradict the license terms under which the vendor received the code.

CodeScoringSonatypeNexus RepositoryEPL 1.0Maven Central
ShareXFacebookLinkedInReddit
Meridian digestThe week's most consequential security stories, distilled into one briefing.See the digest

More in Supply Chain & Open Source

Passwordless Kubernetes Image Pulling with Artifact Keeper via ServiceAccount Tokens
Supply Chain & Open Source

Passwordless Kubernetes Image Pulling with Artifact Keeper via ServiceAccount Tokens

Kubernetes 1.34 and later enables kubelet to forward a pod's ServiceAccount token to an external image credential provider plugin, allowing the plugin to exchange it for short-lived read-only credentials from a compatible registry. Artifact Keeper, an open-source Rust-based OCI and package registry, implements an OIDC provider that validates these tokens and issues temporary credentials without requiring imagePullSecrets in manifests. The approach follows zero-trust principles by eliminating long-lived secrets that can leak across namespaces or clusters. A custom credential provider binary handles the token exchange, enforces audience restrictions, and redacts sensitive data from logs. The solution requires specific ClusterRole permissions for nodes, kubelet flags, and registry-side OIDC mappings that bind Kubernetes namespaces to read-only groups. Testing on kind 1.34.3 confirmed successful pulls for authorized ServiceAccounts and clear 401 errors for unauthorized ones when imagePullPolicy is set to Always.

HabrOct 26, 2026Translated from Russian

Malicious Code Injected into LiteLLM Open Source AI Package via Supply Chain Attack
Supply Chain & Open Source

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.

Security NEXTOct 23, 2026Translated from Japanese

GhostAction Campaign Compromises 790 GitHub Repositories via Malicious Workflows
Supply Chain & Open Source

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.

BoletimSecOct 21, 2026Translated from Portuguese