| ID | PPSA-202611-3 |
|---|---|
| Published | 2026-11-19 |
| Private Packagist Cloud | Affected. Fixed on 2026-11-19. |
| Private Packagist Self-Hosted (KOTS) | Affected <= 2.0.39. Fixed in 2.0.40. |
| Private Packagist Self-Hosted (Helm) | Affected <= 2.0.39. Fixed in 2.0.40. |
Summary
Private Packagist wrote package versions into the markdown of its Microsoft Teams notifications without escaping them. A version could change the content of a release notification with markdown, for example with formatting or links with any text to a website of the attacker. In Slack and Microsoft Teams notifications, a URL or domain in a package version or package name, such as dev-main https://example.com or a package named www.example.com/package, also turned into a link.
Who was affected
Organizations on Private Packagist Cloud until the fix on November 19, 2026, and on Private Packagist Self-Hosted installations running a version before 2.0.40, if all of the following are true:
- The organization has a Microsoft Teams Webhook (Workflow) or Slack Webhook notification channel.
- A malicious user publishes a version or a package of the organization with a crafted version or package name. The attacker can do this as a user of the organization who can add packages, through an artifact upload or a custom package definition, as the operator of a third-party Composer repository the organization mirrors packages from, or by publishing a release of a package from a VCS repository with a
versionin itscomposer.jsonthat has build metadata, the part after a+.
Markdown only changed the content of Microsoft Teams Webhook (Workflow) release notifications. Links from a URL or domain could appear in both Slack and Microsoft Teams notifications: in the version of release notifications, and in the package name of release, abandoned package, publish error and security notifications. A package name cannot contain link syntax or ://, but a vendor with dots, such as www.example.com, is a domain.
Notification channels for email and webhooks were not affected.
Impact
A release notification from Private Packagist in Microsoft Teams could have shown content of the attacker's choice in place of the version:
- Text and formatting that change what the notification says, for example about the release or the package.
- Links with text of the attacker's choice, such as "release notes", next to the View package link, pointing to a website of the attacker.
A notification in Slack or Microsoft Teams could have shown a URL or domain in a version or package name as a link to the attacker's website. Such a link shows its own address as its text, so unlike the markdown links in Microsoft Teams, it could not hide which website it points to.
A reader who trusted the message could have acted on the attacker's content or followed a link to a website of the attacker. The attacker could not run code or access any data in Private Packagist. Only channels of organizations that have the attacker's package would have received such a notification.
What we did
Microsoft Teams notifications now escape markdown in package versions, so they cannot add formatting or links. Package names, versions and organization names in Slack and Microsoft Teams notifications no longer turn into links when they contain a URL or domain. The fix was deployed on Private Packagist Cloud on November 19, 2026, and released in Private Packagist Self-Hosted 2.0.40.
Do customers need to do anything
- Private Packagist Self-Hosted: Upgrade to 2.0.40 or any later version. We recommend upgrading to the latest release.
- Private Packagist Cloud: No action is required.
Credits
Thanks to andikafransisko for reporting this issue.
Start Free Trial
Login to create an organization and start your free trial!