<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="rss.xsl"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Gitea Limited — recent CVEs</title>
    <link>https://vulnogram.org/</link>
    <atom:link href="https://vulnogram.org/rss/gitea" rel="self" type="application/rss+xml"/>
    <description>Most recent CVEs assigned by Gitea Limited (gitea).</description>
    <image>
      <url>https://vulnogram.org/seaview/icons/gitea.png</url>
      <title>Gitea Limited — recent CVEs</title>
      <link>https://vulnogram.org/</link>
    </image>
    <lastBuildDate>Wed, 21 Oct 2026 07:00:07 GMT</lastBuildDate>
    <item>
      <title>CVE-2026-97859 · 6.5 MEDIUM — Gitea API disclosure of private user social graph, keys and stars</title>
      <link>https://vulnogram.org/CVE-2026-97859</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-97859</guid>
      <description>Seven Gitea API routes under `/api/v1/users/{username}` (followers, following, following/{target}, starred, subscriptions, keys and gpg_keys) were registered without the `individualPermsChecker` middleware that enforces the visibility of the target u…</description>
      <category>Medium</category>
      <pubDate>Sun, 18 Oct 2026 19:01:04 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-97204 · 3.1 LOW — Gitea label deletion across repository and organization IDs</title>
      <link>https://vulnogram.org/CVE-2026-97204</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-97204</guid>
      <description>Deleting a label compared the ID of the repository in the request against the organization ID of organization labels, and the two ID sequences overlap. A user with write access to the issues of a repository could therefore delete the labels of an org…</description>
      <category>Low</category>
      <pubDate>Sun, 18 Oct 2026 19:00:50 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-110494 · 6.3 MEDIUM — Gitea release attachment re-linking of issue attachments</title>
      <link>https://vulnogram.org/CVE-2026-110494</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-110494</guid>
      <description>Adding attachments to a release checked the repository and release of an attachment but not whether it was already linked to an issue or comment. A user with write access to the releases of a repository, who knew the UUID of an attachment in that rep…</description>
      <category>Medium</category>
      <pubDate>Sun, 18 Oct 2026 18:57:26 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-110324 · 6.5 MEDIUM — Gitea private profile information disclosure through POST request</title>
      <link>https://vulnogram.org/CVE-2026-110324</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-110324</guid>
      <description>The visibility check of Gitea user profiles was applied to GET requests only, while `POST /{username}` (follow and unfollow) required only a signed-in user. Any authenticated user could therefore obtain the full name, location, website and descriptio…</description>
      <category>Medium</category>
      <pubDate>Sun, 18 Oct 2026 18:57:20 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-110311 · 4.3 MEDIUM — Gitea draft release creation disclosing attachment metadata</title>
      <link>https://vulnogram.org/CVE-2026-110311</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-110311</guid>
      <description>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 receive…</description>
      <category>Medium</category>
      <pubDate>Sun, 18 Oct 2026 18:57:14 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-109844 · 4.3 MEDIUM — Gitea watched repositories API disclosure after access revocation</title>
      <link>https://vulnogram.org/CVE-2026-109844</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-109844</guid>
      <description>`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…</description>
      <category>Medium</category>
      <pubDate>Sun, 18 Oct 2026 18:57:08 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-107686 · 4.3 MEDIUM — Gitea reactions accepted on locked issues and comments</title>
      <link>https://vulnogram.org/CVE-2026-107686</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-107686</guid>
      <description>The Gitea web handlers for adding and removing reactions on issues and comments did not refuse locked issues for users without write access, although the API did. A signed-in user who could read an issue could therefore add or remove reactions on a l…</description>
      <category>Medium</category>
      <pubDate>Sun, 18 Oct 2026 18:56:59 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-107618 — Gitea cross-site request forgery on repository topics</title>
      <link>https://vulnogram.org/CVE-2026-107618</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-107618</guid>
      <description>`POST /{owner}/{repo}/topics` was registered without the sign-in middleware that provides the cross-origin protection, so a request issued by a third-party site was not rejected. A repository administrator who visited a malicious page could have the…</description>
      <pubDate>Sun, 18 Oct 2026 18:56:53 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-105964 · 6.5 MEDIUM — Gitea Actions artifact v4 API unbounded request body</title>
      <link>https://vulnogram.org/CVE-2026-105964</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-105964</guid>
      <description>The Gitea Actions artifact v4 (Twirp) handlers read the whole request body into memory without a size limit. A user who can run a workflow and obtains the runner token of that run could send an oversized request to the artifact service and exhaust th…</description>
      <category>Medium</category>
      <pubDate>Sun, 18 Oct 2026 18:56:47 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-105661 · 5.3 MEDIUM 🌩️ — Gitea panic on the repositories route of individual users</title>
      <link>https://vulnogram.org/CVE-2026-105661</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-105661</guid>
      <description>Requesting `/{username}/-/repositories` for an individual user instead of an organization made the organization home handler dereference a nil organization and panic. The request needs no authentication and no special configuration. The server answer…</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Sun, 18 Oct 2026 18:56:41 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-109553 · 7.5 HIGH — Gitea SSH certificate principal impersonation of other users</title>
      <link>https://vulnogram.org/CVE-2026-109553</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-109553</guid>
      <description>Gitea resolved the principals of an SSH certificate by searching the content of all stored public keys instead of only principal keys. When Gitea trusts a user certificate authority (`SSH_TRUSTED_USER_CA_KEYS`) and accepts arbitrary principals (`SSH_…</description>
      <category>High</category>
      <pubDate>Sun, 18 Oct 2026 18:51:31 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-104627 · 5.4 MEDIUM 🌩️ — Gitea OpenID account linking without session binding</title>
      <link>https://vulnogram.org/CVE-2026-104627</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-104627</guid>
      <description>The Gitea OpenID association callback in the security settings accepted a positive OpenID 2.0 assertion without checking that the signed-in user had started the linking. Because OpenID 2.0 allows unsolicited assertions, an attacker-controlled OpenID…</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Sun, 18 Oct 2026 18:51:06 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-78433 · 5.9 MEDIUM 🌩️ — Gitea private attachment disclosure through repository mismatch</title>
      <link>https://vulnogram.org/CVE-2026-78433</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-78433</guid>
      <description>Gitea&apos;s web attachment handler skips its cross-repository ownership check for attachments created before 16 January 2026 and checks permissions against the repository named in the request URL instead. An unauthenticated attacker who knows a private a…</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 14 Oct 2026 14:38:17 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-78231 · 5.3 MEDIUM 🌩️ — Gitea blind SSRF through OpenID assertion verification</title>
      <link>https://vulnogram.org/CVE-2026-78231</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-78231</guid>
      <description>When OpenID sign-in is enabled, Gitea processes unauthenticated assertion parameters and sends an HTTP POST request to the caller-supplied OpenID provider endpoint during verification. An attacker controls the destination and much of the form body, a…</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 14 Oct 2026 14:38:10 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-73814 · 6.5 MEDIUM — Gitea repository ownership escalation by administrators</title>
      <link>https://vulnogram.org/CVE-2026-73814</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-73814</guid>
      <description>Gitea&apos;s collaboration access-mode endpoint accepts the Owner access mode from an authenticated repository collaborator with Admin access. The collaborator can promote their effective permissions from Admin to Owner and then perform owner-only operati…</description>
      <category>Medium</category>
      <pubDate>Wed, 14 Oct 2026 14:38:05 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-73804 · 8.1 HIGH — Gitea API token scope escalation through HTTP signatures</title>
      <link>https://vulnogram.org/CVE-2026-73804</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-73804</guid>
      <description>Gitea allows a token with write:user scope to register an attacker-controlled SSH public key on the token owner&apos;s account. API requests signed with the corresponding private key authenticate as that account through HTTP Signature without API token sc…</description>
      <category>High</category>
      <pubDate>Wed, 14 Oct 2026 14:38:00 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-73802 · 8.8 HIGH — Gitea Runner host isolation bypass through container options</title>
      <link>https://vulnogram.org/CVE-2026-73802</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-73802</guid>
      <description>Gitea Runner passes workflow-controlled container options into Docker job container configuration while privileged mode is disabled. Host namespace settings, expanded capabilities, and security profile overrides can remain effective despite Privilege…</description>
      <category>High</category>
      <pubDate>Wed, 14 Oct 2026 14:37:55 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-73800 · 8.8 HIGH — Gitea reusable workflow secret exposure in pull_request_target</title>
      <link>https://vulnogram.org/CVE-2026-73800</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-73800</guid>
      <description>Gitea resolves local reusable workflow files from a fork&apos;s head commit when a trusted base-branch workflow runs for a pull_request_target event. A fork author can modify a referenced reusable workflow so attacker-controlled code executes with the rep…</description>
      <category>High</category>
      <pubDate>Wed, 14 Oct 2026 14:37:49 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-73539 · 7.5 HIGH — Gitea external renderer argument injection and code execution</title>
      <link>https://vulnogram.org/CVE-2026-73539</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-73539</guid>
      <description>Gitea substitutes a URL derived from the markup Context field into external renderer command templates without escaping the reference path before shell-style argument splitting. A crafted Context can inject additional renderer arguments, including op…</description>
      <category>High</category>
      <pubDate>Wed, 14 Oct 2026 14:37:44 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-73535 · 8.8 HIGH — Gitea second-factor bypass through OpenID identity linking</title>
      <link>https://vulnogram.org/CVE-2026-73535</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-73535</guid>
      <description>Gitea&apos;s OpenID connect handler accepts a user&apos;s password without enforcing enrolled TOTP or WebAuthn verification before completing sign-in and linking an OpenID identifier. When OpenID sign-in is enabled, an attacker who knows the victim&apos;s password…</description>
      <category>High</category>
      <pubDate>Wed, 14 Oct 2026 14:37:39 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-73273 · 4.3 MEDIUM — Gitea Maven checksum upload quota bypass and memory exhaustion</title>
      <link>https://vulnogram.org/CVE-2026-73273</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-73273</guid>
      <description>Gitea&apos;s Maven upload handler reads checksum uploads entirely into memory and returns before enforcing package-size quotas. An authenticated user with package-publish permission can submit an oversized body to a checksum endpoint despite legitimate ch…</description>
      <category>Medium</category>
      <pubDate>Wed, 14 Oct 2026 14:37:30 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-73135 · 5.3 MEDIUM 🌩️ — Gitea hidden-owner repository listing disclosure</title>
      <link>https://vulnogram.org/CVE-2026-73135</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-73135</guid>
      <description>Gitea uses inconsistent repository visibility predicates, and the condition used by some repository-listing endpoints admits repositories whose owners are hidden from the viewer. Those listings disclose repository metadata even though direct routes c…</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 14 Oct 2026 14:37:25 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-73130 · 4.3 MEDIUM — Gitea repository initialization resource exhaustion</title>
      <link>https://vulnogram.org/CVE-2026-73130</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-73130</guid>
      <description>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…</description>
      <category>Medium</category>
      <pubDate>Wed, 14 Oct 2026 14:37:20 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-73126 · 4.3 MEDIUM — Gitea private workflow badge token scope bypass</title>
      <link>https://vulnogram.org/CVE-2026-73126</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-73126</guid>
      <description>Gitea&apos;s Actions workflow status badge endpoint does not enforce repository-read scope or the public-only restriction on the token authenticating the request. A token lacking read:repository, or restricted to public repositories, can retrieve the late…</description>
      <category>Medium</category>
      <pubDate>Wed, 14 Oct 2026 14:37:15 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-71301 · 4.3 MEDIUM — Gitea private pull request title disclosure through markup</title>
      <link>https://vulnogram.org/CVE-2026-71301</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-71301</guid>
      <description>Gitea&apos;s repository markup endpoint resolves same-repository pull request references without enforcing the viewer&apos;s Pull Requests permission. A member with only Wiki access to a private repository can submit a markup preview request and retrieve a pri…</description>
      <category>Medium</category>
      <pubDate>Wed, 14 Oct 2026 14:37:10 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-71184 · 8.8 HIGH — Gitea fork workflow approval bypass through review events</title>
      <link>https://vulnogram.org/CVE-2026-71184</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-71184</guid>
      <description>Gitea&apos;s pull request review notifier does not attach the pull request to the Actions notification, so the fork workflow approval gate does not recognize the run as originating from a fork. Review comment and review approval or rejection events can co…</description>
      <category>High</category>
      <pubDate>Wed, 14 Oct 2026 14:37:05 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-70407 · 4.3 MEDIUM — Gitea organization listing token scope bypass</title>
      <link>https://vulnogram.org/CVE-2026-70407</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-70407</guid>
      <description>Gitea&apos;s organization-list API does not enforce the read:organization token scope. A token limited to another category, such as read:misc, can retrieve organization metadata visible to its owner. For a site administrator&apos;s token, the response can incl…</description>
      <category>Medium</category>
      <pubDate>Wed, 14 Oct 2026 14:36:59 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-70406 · 6.5 MEDIUM — Gitea private comparison disclosure with public-only tokens</title>
      <link>https://vulnogram.org/CVE-2026-70406</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-70406</guid>
      <description>Gitea&apos;s shared comparison helper omits the token repository-access check used when updating pull requests. A public-only token with read:repository scope can route a comparison or pull request creation through a public base repository and retrieve co…</description>
      <category>Medium</category>
      <pubDate>Wed, 14 Oct 2026 14:36:53 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-70402 · 5.8 MEDIUM — Gitea local code execution through writable Git hooks</title>
      <link>https://vulnogram.org/CVE-2026-70402</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-70402</guid>
      <description>Gitea creates server-side Git hook directories and scripts with mode 0777 and relies on the process umask to restrict access. With a permissive umask such as 0000 or 0002, another local user who can reach the repository storage may modify a hook or a…</description>
      <category>Medium</category>
      <pubDate>Wed, 14 Oct 2026 14:36:46 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-70400 · 5.4 MEDIUM — Gitea private migration creation with public-only tokens</title>
      <link>https://vulnogram.org/CVE-2026-70400</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-70400</guid>
      <description>Gitea&apos;s repository migration API accepts a public-only token when the request specifies creation of a private repository. A delegated token intended to operate only on public resources can create a private repository and migration task under the auth…</description>
      <category>Medium</category>
      <pubDate>Wed, 14 Oct 2026 14:36:41 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-70396 · 5.4 MEDIUM — Gitea organization repository creation token scope bypass</title>
      <link>https://vulnogram.org/CVE-2026-70396</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-70396</guid>
      <description>Gitea&apos;s organization repository-creation API requires write:organization but omits the write:repository token scope enforced by other repository-creation routes. A personal access token or OAuth application token without repository-write scope can th…</description>
      <category>Medium</category>
      <pubDate>Wed, 14 Oct 2026 14:36:36 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-68964 · 4.3 MEDIUM — Gitea restricted-user SSH and GPG key metadata disclosure</title>
      <link>https://vulnogram.org/CVE-2026-68964</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-68964</guid>
      <description>Gitea&apos;s user SSH and GPG key-list API endpoints omit the profile visibility check applied by their web equivalents. A restricted account can retrieve public keys, key titles, fingerprints, and GPG-embedded email addresses belonging to Limited-visibil…</description>
      <category>Medium</category>
      <pubDate>Wed, 14 Oct 2026 14:36:28 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-68957 · 4.3 MEDIUM — Gitea restricted-user issue search disclosure</title>
      <link>https://vulnogram.org/CVE-2026-68957</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-68957</guid>
      <description>Gitea&apos;s API and web issue-search paths do not treat restricted accounts as anonymous viewers when evaluating Limited-visibility repository owners. A restricted user can search and retrieve issue titles and bodies that should be hidden by the owner&apos;s…</description>
      <category>Medium</category>
      <pubDate>Wed, 14 Oct 2026 14:36:22 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-67577 · 4.3 MEDIUM — Gitea restricted-user activity and heatmap disclosure</title>
      <link>https://vulnogram.org/CVE-2026-67577</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-67577</guid>
      <description>Gitea&apos;s activity-feed and contribution-heatmap API handlers do not apply the profile visibility check for restricted accounts viewing Limited-visibility users. A restricted user can retrieve activity records and contribution timestamps that the corre…</description>
      <category>Medium</category>
      <pubDate>Wed, 14 Oct 2026 14:36:16 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-66877 · 8.1 HIGH — Gitea fork workflow approval bypass through concurrency cancellation</title>
      <link>https://vulnogram.org/CVE-2026-66877</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-66877</guid>
      <description>Gitea enforces first-time fork contributor approval by blocking jobs, but some job transition and dispatch paths do not re-check the run&apos;s approval requirement. A separate run sharing a job-level concurrency group can cancel a pending job and cause i…</description>
      <category>High</category>
      <pubDate>Wed, 14 Oct 2026 14:36:11 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-66874 · 6.5 MEDIUM — Gitea required Actions check bypass through skipped workflows</title>
      <link>https://vulnogram.org/CVE-2026-66874</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-66874</guid>
      <description>For pull request events, Gitea reads workflow definitions from the pull request head and posts a synthetic skipped status when workflow branch or path filters exclude execution. A fork pull request author can supply a workflow matching a required sta…</description>
      <category>Medium</category>
      <pubDate>Wed, 14 Oct 2026 14:36:06 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-66853 · 4.3 MEDIUM — Gitea restricted-user organization metadata disclosure</title>
      <link>https://vulnogram.org/CVE-2026-66853</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-66853</guid>
      <description>Gitea&apos;s user organization-list API includes Limited-visibility organizations for authenticated restricted accounts without applying the visibility restriction enforced by the single-organization endpoint. A restricted user can list a known user&apos;s pub…</description>
      <category>Medium</category>
      <pubDate>Wed, 14 Oct 2026 14:36:01 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-66849 · 4.3 MEDIUM — Gitea restricted-user package visibility bypass</title>
      <link>https://vulnogram.org/CVE-2026-66849</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-66849</guid>
      <description>Gitea&apos;s package registry grants authenticated users read access to packages owned by Limited-visibility users without excluding restricted accounts. A restricted user can enumerate and download those packages despite the visibility policy that should…</description>
      <category>Medium</category>
      <pubDate>Wed, 14 Oct 2026 14:35:55 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-63792 · 5.3 MEDIUM — Gitea private reusable workflow disclosure to fork runs</title>
      <link>https://vulnogram.org/CVE-2026-63792</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-63792</guid>
      <description>Gitea&apos;s collaborative-owner authorization path for reading cross-repository reusable workflows does not exclude fork pull request runs. An approved fork workflow targeting a private repository can read workflow files from another private repository t…</description>
      <category>Medium</category>
      <pubDate>Wed, 14 Oct 2026 14:29:01 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-63021 · 6.5 MEDIUM — Gitea Swift package manifest memory exhaustion</title>
      <link>https://vulnogram.org/CVE-2026-63021</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-63021</guid>
      <description>Gitea&apos;s Swift package parser limits each manifest to 128 KiB but does not limit the number of manifests or their aggregate size before reading them into memory. An authenticated user with package-publish permission can upload a highly compressed arch…</description>
      <category>Medium</category>
      <pubDate>Wed, 14 Oct 2026 14:28:56 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-62925 · 6.5 MEDIUM — Gitea Alpine package parsing memory exhaustion</title>
      <link>https://vulnogram.org/CVE-2026-62925</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-62925</guid>
      <description>Gitea parses Alpine package uploads before enforcing package-size quotas and does not bound the decompressed .PKGINFO data or its dependency and provides entry counts. An authenticated user with package-publish permission can upload a small, highly c…</description>
      <category>Medium</category>
      <pubDate>Wed, 14 Oct 2026 14:28:51 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-60021 · 6.5 MEDIUM — Gitea GitLab migration denial of service</title>
      <link>https://vulnogram.org/CVE-2026-60021</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-60021</guid>
      <description>Gitea&apos;s initial GitLab migration version probe uses an HTTP client without a timeout and does not attach the migration task&apos;s cancellation context. An authenticated user who can start migrations can target an attacker-controlled server that keeps the…</description>
      <category>Medium</category>
      <pubDate>Wed, 14 Oct 2026 14:28:46 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-60018 · 6.5 MEDIUM — Gitea OneDev migration denial of service</title>
      <link>https://vulnogram.org/CVE-2026-60018</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-60018</guid>
      <description>Gitea&apos;s OneDev migration downloader reads the entire remote version response into memory without a size limit and uses a client without a timeout. An authenticated user who can start a repository migration can direct it to an attacker-controlled OneD…</description>
      <category>Medium</category>
      <pubDate>Wed, 14 Oct 2026 14:28:41 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-60010 · 6.5 MEDIUM — Gitea organization team policy bypass through repository API</title>
      <link>https://vulnogram.org/CVE-2026-60010</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-60010</guid>
      <description>Gitea&apos;s repository-side team-link API allows a repository administrator who is not an organization owner to attach organization teams to a repository despite RepoAdminChangeTeamAccess being disabled. The endpoint does not enforce the organization&apos;s r…</description>
      <category>Medium</category>
      <pubDate>Wed, 14 Oct 2026 14:28:36 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-60008 · 3.5 LOW — Gitea Jupyter notebook UI redress through CSS class injection</title>
      <link>https://vulnogram.org/CVE-2026-60008</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-60008</guid>
      <description>Gitea&apos;s Jupyter notebook renderer inserts the notebook&apos;s language_info.name metadata into a CSS class attribute while disabling sanitization and rendering directly in the main document without an iframe sandbox. A malicious repository notebook can su…</description>
      <category>Low</category>
      <pubDate>Wed, 14 Oct 2026 14:28:31 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-59774 · 9.8 CRITICAL 🌩️ — Gitea Org-mode file disclosure and code execution</title>
      <link>https://vulnogram.org/CVE-2026-59774</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-59774</guid>
      <description>Gitea&apos;s Org-mode markup renderer processes INCLUDE directives supplied to the repository markup endpoint without preventing access to server-side files. An unauthenticated attacker can use a suitable public repository to read files accessible to the…</description>
      <category>Critical</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 14 Oct 2026 14:28:25 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-59766 · 4.3 MEDIUM — Gitea private repository metadata disclosure after access revocation</title>
      <link>https://vulnogram.org/CVE-2026-59766</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-59766</guid>
      <description>Gitea&apos;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 reposi…</description>
      <category>Medium</category>
      <pubDate>Wed, 14 Oct 2026 14:28:20 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-25946 · 5.3 MEDIUM 🌩️ — Gitea OpenID discovery server-side request forgery</title>
      <link>https://vulnogram.org/CVE-2026-25946</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-25946</guid>
      <description>When OpenID sign-in is enabled, Gitea accepts a user-supplied OpenID URL and performs discovery requests without validating the destination against internal network addresses. An unauthenticated remote attacker can cause the server to contact loopbac…</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 14 Oct 2026 14:28:15 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-97626 · 4.3 MEDIUM — Gitea profile feed disclosure bypassing user visibility</title>
      <link>https://vulnogram.org/CVE-2026-97626</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-97626</guid>
      <description>Requesting a user or organization profile page (`GET /{username}`) with an `Accept: application/rss+xml` or `Accept: application/atom+xml` header returned the owner&apos;s activity feed without the visibility check that the profile page and the `.rss` and…</description>
      <category>Medium</category>
      <pubDate>Tue, 06 Oct 2026 21:36:48 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-96594 · 6.1 MEDIUM 🌩️ — Gitea repository media API stored XSS</title>
      <link>https://vulnogram.org/CVE-2026-96594</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-96594</guid>
      <description>The Gitea API endpoint `GET /api/v1/repos/{owner}/{repo}/media/{filepath}` wrote files of up to 1 KiB that are stored directly in Git, not in LFS, to the response without the content type and disposition headers Gitea uses for user content. An HTML f…</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Tue, 06 Oct 2026 21:36:38 GMT</pubDate>
    </item>
  </channel>
</rss>
