CVE-2026-106506

The Backstage framework is vulnerable to improper input validation within the @backstage/plugin-scaffolder-backend package in versions prior to 4.1.0 . This flaw exists in the scaffolder task list ordering functionality, potentially allowing an authenticated user with permissions to create and re...

CVE-2026-106505

The @backstage/plugin-techdocs-node package in the Backstage framework is vulnerable to a bypass of the MkDocs configuration sanitizer in the TechDocs backend. Affected versions are those prior to 1.14.6 and 1.15.4 . An attacker with permissions to commit changes to a repository using TechDocs ca...

CVE-2026-106505 Backstage: Bypass of MkDocs configuration sanitizer in TechDocs backend

Backstage is an open framework for building developer portals. Prior to 1.14.6 and 1.15.4, the @backstage/plugin-techdocs-node package is affected by bypass of mkdocs configuration sanitizer in techdocs backend. Users with the ability to commit changes to a repository that uses TechDocs can...

CVE-2026-106504 Backstage: Sensitive information exposure in scaffolder task logs

Backstage is an open framework for building developer portals. Prior to 4.1.0, the @backstage/plugin-scaffolder-backend package is affected by sensitive information exposure in scaffolder task logs. An authenticated user who can create and read scaffolder tasks may be able to observe sensitive...

CVE-2026-106504

The Backstage framework is vulnerable in the @backstage/plugin-scaffolder-backend package prior to version 4.1.0 . The root cause is sensitive information exposure within scaffolder task logs. An authenticated user capable of creating and reading tasks can observe sensitive values if a deployment...

CVE-2026-106503 Backstage: Scaffolder action input authorization bypass

Backstage is an open framework for building developer portals. Prior to 3.3.1, 3.4.1, 4.0.3 and 4.1.0, the @backstage/plugin-scaffolder-backend package is affected by scaffolder action input authorization bypass. An authenticated user with access to affected Scaffolder templates could bypass...

CVE-2026-106503

The Backstage framework's @backstage/plugin-scaffolder-backend package is vulnerable to a scaffolder action input authorization bypass in versions prior to 3.3.1, 3.4.1, 4.0.3, and 4.1.0. An authenticated user with access to affected Scaffolder templates can bypass configured action restrictions....

CVE-2026-97626

In Gitea , a vulnerability exists where requesting a user or organization profile page (GET /{username}) with specific Accept headers (application/rss+xml or application/atom+xml) bypasses visibility checks. This allows anonymous users , restricted users , and non-members to confirm the existence...

CVE-2026-97626 Gitea profile feed disclosure bypassing user visibility

Requesting a user or organization profile page GET /username with an Accept: application/rss+xml or Accept: application/atom+xml header returned the owner's activity feed without the visibility check that the profile page and the .rss and .atom routes apply. Anonymous users, restricted users and...

CVE-2026-96594

The Gitea repository media API endpoint GET /api/v1/repos/{owner}/{repo}/media/{filepath} is vulnerable to stored Cross-Site Scripting (XSS) . The root cause is that the API fails to return appropriate content-type and disposition security headers when serving small files (up to 1 KiB) stored dir...

CVE-2026-89182 Gitea push-to-create bypass of FORCE_PRIVATE policy

With repository FORCEPRIVATE = true, Gitea creates new repositories as private, but the post-receive hook still applied the repo.private=false push option to an empty repository created by push. Any user who can create repositories could make their new repository public in violation of the instan...

CVE-2026-89182

A flaw in Gitea allows authenticated users with repository creation privileges to bypass instance privacy policies. When [repository] FORCE_PRIVATE = true is enabled, the post-receive hook incorrectly applies the repo.private=false push option to empty repositories created via push. This allows u...

CVE-2026-105268

The Gitea application contains an authorization flaw in its issue attachment API routes (/api/v1/repos/{owner}/{repo}/issues/{index}/assets/{attachment_id}). The vulnerability allows a user who opened an issue to rename or delete attachments that were actually posted in comments by other users. T...

CVE-2026-105267

The Gitea web route for deleting tags (POST /{owner}/{repo}/tags/delete) contains a flaw where it shares request handling logic with release deletion without verifying if the target is a plain tag. This allows an authenticated collaborator with Code write permissions (but lacking Releases write a...

CVE-2026-105267 Gitea tag delete route deletes releases without release permission

The Gitea web route for deleting tags POST /owner/repo/tags/delete requires only write access to the Code unit, but shares its handler with release deletion and did not check that the target was a plain tag. A collaborator with Code write access and without Releases write access could permanently...

CVE-2026-104633

A flaw in Gitea allows for a Denial of Service (DoS) via memory exhaustion during repository migrations from another instance. The vulnerability occurs because Gitea relies on the source server's reported max_response_items (or max_response_items) to determine the end of paginated downloads. If a...

CVE-2026-101023

A flaw in Gitea allows an attacker or user to maintain persistent access to the application. The OAuth2 token endpoint validates the signature and grant of a token submitted with the refresh_token grant type but fails to verify that the submitted token is specifically a refresh token . Consequent...

CVE-2026-101023 Gitea OAuth2 refresh token grant accepts access tokens

Gitea's OAuth2 token endpoint verified the signature and grant of a token submitted with the refreshtoken grant type, but not that the token was a refresh token. An unexpired access token for the same OAuth2 application and grant could be exchanged for a new access token and refresh token. Whoeve...

CVE-2026-106502

The Backstage framework, specifically the @backstage/plugin-scaffolder-backend package in versions prior to 4.1.0 , contains a vulnerability where sensitive information may be exposed in Scaffolder task failure events . Under specific template and failure conditions, an authenticated user could r...

CVE-2026-106501

The Backstage open framework for developer portals is vulnerable to sensitive information exposure in the @backstage/plugin-scaffolder-backend package. Prior to versions 3.3.1, 3.4.1, 4.0.3, and 4.1.0 , an authenticated user capable of reading another user's Scaffolder task can access internal ex...