forgejo-keys-idor

abraxaslabs.tech · github.com/abraxas · @abraxasnull · [email protected] · forgejo-keys-idor forgejo-keys-idor Class: IDOR Reach: Remote Forgejo 16.0.5 8d24b7d - Forgejo GET /api/v1/user/keys/id sits in the current-user group reqToken, user scope. The handler still loads publickey by numeric...

CVE-2026-109844

GET /api/v1/user/subscriptions returned the metadata of every repository a user was watching without checking that the user still had access to it. A user who watched a private repository while having access, and later lost it, for example through a team permission downgrade, could still read its...

CVE-2026-109844 Gitea watched repositories API disclosure after access revocation

GET /api/v1/user/subscriptions returned the metadata of every repository a user was watching without checking that the user still had access to it. A user who watched a private repository while having access, and later lost it, for example through a team permission downgrade, could still read its...

CVE-2026-109844

The Gitea repository management platform is affected by a vulnerability where the GET /api/v1/user/subscriptions endpoint fails to verify if a user still maintains access to a watched repository. Consequently, a user who previously had access to a private repository but subsequently lost those pe...

CVE-2026-59766

Gitea's starred-repository and tracked-time API endpoints do not re-check current repository permissions before returning data associated with the requesting user. A user whose access to a private repository has been revoked can still retrieve repository metadata through /api/v1/user/starred and...

CVE-2026-73804

Gitea allows a token with write:user scope to register an attacker-controlled SSH public key on the token owner's account. API requests signed with the corresponding private key authenticate as that account through HTTP Signature without API token scope information, causing route-level token scop...

CVE-2026-73130

Gitea does not limit the length of the gitignores field accepted by repository-creation forms and the API. Repository initialization splits the field into template names, repeatedly reads the referenced templates, and buffers their contents in memory. An attacker who can create repositories can...

EUVD-2026-101280

Gitea's starred-repository and tracked-time API endpoints do not re-check current repository permissions before returning data associated with the requesting user. A user whose access to a private repository has been revoked can still retrieve repository metadata through /api/v1/user/starred and...

GHSA-88F6-4RJV-X774 Vikunja: TOTP secret is readable after enrollment, no step-up auth

Summary Once a user has TOTP enabled, the API still hands back the raw shared secret to anyone holding that account's access token. Reading it doesn't ask for the password, even though disabling TOTP does. So a stolen token, an XSS, or a browser left open is enough to copy the second factor into...

Vikunja: TOTP secret is readable after enrollment, no step-up auth

Summary Once a user has TOTP enabled, the API still hands back the raw shared secret to anyone holding that account's access token. Reading it doesn't ask for the password, even though disabling TOTP does. So a stolen token, an XSS, or a browser left open is enough to copy the second factor into...

Gitea API Disclosure Protected Information

The vulnerability of the /api/v1/user/starred and /api/v1/user/subscriptions endpoints of the Git repository management system Gitea is related to insufficient protection of sensitive data. Exploiting this vulnerability could allow a malicious actor to disclose protected information...

Gitea API Disclosure Sensitive Information

The vulnerability of endpoints /api/v1/user/orgs and /api/v1/users/username/orgs/org/permissions in the Git repository management system Gitea is related to access control deficiencies. Exploiting this vulnerability could allow a malicious actor to disclose sensitive information...

Duplicate Advisory: Vikunja: TOTP secret is readable after enrollment, no step-up auth

Duplicate Advisory This advisory has been withdrawn because it is a duplicate of GHSA-88f6-4rjv-x774. This link is maintained to preserve external references. Original Description Vikunja before 2.6.0 continues to expose the raw TOTP shared secret after enrollment through the GET...

GHSA-JMR8-R558-3JHX Duplicate Advisory: Vikunja: TOTP secret is readable after enrollment, no step-up auth

Duplicate Advisory This advisory has been withdrawn because it is a duplicate of GHSA-88f6-4rjv-x774. This link is maintained to preserve external references. Original Description Vikunja before 2.6.0 continues to expose the raw TOTP shared secret after enrollment through the GET...

CVE-2026-91982

Vikunja before 2.6.0 continues to expose the raw TOTP shared secret after enrollment through the GET /api/v1/user/settings/totp and /api/v1/user/settings/totp/qrcode endpoints without re-authentication. Attackers with a valid access token can read the secret, import it into their own authenticato...

CVE-2026-91982: Insufficiently Protected Credentials

Vikunja before 2.6.0 continues to expose the raw TOTP shared secret after enrollment through the GET /api/v1/user/settings/totp and /api/v1/user/settings/totp/qrcode endpoints without re-authentication. Attackers with a valid access token can read the secret, import it into their own authenticato...

CVE-2026-24791

Public-only tokens bypass private-resource restrictions on /api/v1/user self routes...

CVE-2026-24791: Incorrect Authorization

Public-only tokens bypass private-resource restrictions on /api/v1/user self routes...

CVE-2026-59766

CVE-2026-20800 fixed private-info leakage to revoked users only for the notification endpoint. Two sibling endpoints that return data keyed on the caller's own relationship still do not re-check repo access at output time: - "GET /api/v1/user/starred" — "getStarredRepos" computes a per-repo...

CVE-2026-56276: Improperly Controlled Modification of Dynamically-Determined Object Attributes

Flowise before 3.1.2 contains a mass assignment vulnerability in the PUT /api/v1/user endpoint that allows authenticated users to directly modify the credential field without validation. Attackers can bypass password change verification and session invalidation by supplying a crafted password has...