Live › vulnerability › CVE-2026-110311
Go to dashboardCreating a draft release through the API returned an assets list built from a release without an ID, which matched every attachment not linked to a release. A user who could create draft releases received file names, UUIDs, upload times, sizes and download counts for attachments in repositories they cannot read.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Teams running a self-hosted code forge with a release API where some users can create draft releases in repositories they do not fully control. Instances where only maintainers or admins create releases, or where no repositories are private, are less exposed. The sources do not name the product or the fixed version.
No product ranges from the sources yet.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Creating a draft release through the API returned an assets list that was built from a release without an ID, which matched every attachment that was not linked to a release. A user who could create a draft release in a repository therefore received the metadata (file name, UUID, upload time, size and download count) of issue and comment attachments of repositories they could not read, and of abandoned uploads.
This page as .md · .json · in your agent: get_signal("CVE-2026-110311")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.