{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-67577 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-67577 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-67577 is a medium-severity vulnerability in Gitea, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-67577 and fix it if it is affected.\n\nWhat it is: CVE-2026-67577 is a medium-severity vulnerability in Gitea, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-67577 in the wild and no public exploit code.\n\nAffected product: Gitea. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-67577/ (Markdown: https://insights.sbomify.com/CVE-2026-67577/index.md)","id":"CVE-2026-67577","markdown":"https://insights.sbomify.com/CVE-2026-67577/index.md","name":"CVE-2026-67577","record":{"aliases":["GHSA-rfm6-r2x5-cg56"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Gitea self-hosted git","requires_auth":"low_privilege","summary":"Restricted users can bypass profile visibility checks to view private activity data of limited-visibility users via API endpoints.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Gitea","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Gitea restricted-user activity and heatmap disclosure","id":"CVE-2026-67577","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"Missing authorization in FA-50","id":"CVE-2026-67578"},"packages":[],"prev":{"headline":"Mira Hormone Monitor, Mira Android App Use of Hard-coded Credentials","id":"CVE-2026-67568"},"products":["Gitea"],"published":"2026-10-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-14","vendors":["Gitea"]},"summary":"Restricted users can bypass profile visibility checks to view private activity data of limited-visibility users via API endpoints.","url":"https://insights.sbomify.com/CVE-2026-67577/"}