CVE-2026-67577

What it is

Gitea'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 corresponding profile routes deny. Exposed activity can include repository names, commit messages, and issue or pull request events associated with qualifying public-repository activity.

At a glance

Exploitability

Can be exploited over the network with a low-privilege account. Limited direct impact.

Exploit odds

0.4% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-10-14 15:17 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-14 16:17 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.4% in the next 30 days (EPSS).
• Severity: 4.3 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-10-14 15:17 UTC

Last modified

2026-10-14 16:17 UTC

Exploit probability

0.4% · EPSS, next 30 days

Weakness

CWE-284 · Improper access control

Record status

Deferred

Attack profile CVSS 3.1 · 4.3

Attack vector

Network

Complexity

Low

Privileges needed

Low

User interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-67577.md and follow it. Check whether this project is affected by CVE-2026-67577. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge