Skip to main content
Mallory
HighVulnerability

CVE-2021-45326: CSRF in Gitea API routes before 1.5.2

Published Feb 8, 2022 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.8High · v3.1
EPSS0.61%50th percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
Vendor
Gitea
IdentifiersCVE-2021-45326CWE-352 · Cross-Site Request Forgery (CSRF)

A Cross Site Request Forgery (CSRF) vulnerability exists in Gitea versions prior to 1.5.2, affecting API routes. The vulnerability allows attackers to trick authenticated users into submitting state-altering POST requests without their consent, potentially leading to unauthorized actions being performed on behalf of the user.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Exploitation of this vulnerability could allow an attacker to perform unauthorized actions via the API as an authenticated user, such as modifying repositories, user settings, or other sensitive operations, depending on the permissions of the victim.

Mitigation

If you can’t patch tonight, do this now.

As an interim measure, restrict access to the Gitea instance to trusted networks, ensure users are aware of CSRF risks, and consider implementing additional CSRF protections at the reverse proxy or web application firewall level until the software is updated.

Remediation

Patch, then assume compromise.

Upgrade Gitea to version 1.5.2 or later, where the CSRF vulnerability in API routes has been addressed.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GiteaGiteaapplication
FAQ

Frequently asked questions

Is CVE-2021-45326 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2021-45326?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2021-45326.
Is there a patch for CVE-2021-45326?
Upgrade Gitea to version 1.5.2 or later, where the CSRF vulnerability in API routes has been addressed.
What products are affected by CVE-2021-45326?
Gitea.
How severe is CVE-2021-45326?
CVE-2021-45326 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 0.61% (50th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence1Every report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.