Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

CVE-2026-60008— Gitea Jupyter notebook UI redress through CSS class injection

Quick assessment

Affected
Gitea Gitea
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Gitea 的 Jupyter Notebook 渲染器在未启用内容安全策略(即禁用了 HTML 清理机制)的情况下,将 notebook 的 元数据直接插入到 CSS 类属性中,并在主文档中直接渲染,而未使用 iframe 沙箱环境。恶意仓库中的 notebook 可以构造包含多个 CSS 类的结构,这些类能够创建一个覆盖整个视口的透明层,从而在用户浏览时拦截鼠标点击事件。报告指出的主要影响为 UI 重定向(UI redress)攻击,但未证实存在脚本执行问题。

AI Predicted 6.5 Difficulty: Easy EPSS 0.37% · P29

Affected Version Matrix 1

VendorProduct Version RangeStatus
Gitea Gitea 1.27.0≤ 1.27.1 affected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-60008

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Gitea Jupyter notebook UI redress through CSS class injection
Source: CVE Program / CVE List V5
Vulnerability Description
Gitea's Jupyter notebook renderer inserts the notebook'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 supply multiple CSS classes that create a viewport-covering overlay and intercept clicks when another user views it. The reported impact is UI redress; script execution was not demonstrated.
Source: CVE Program / CVE List V5
CVSS Information
N/A
Source: CVE Program / CVE List V5
Vulnerability Type
在Web页面生成时对输入的转义处理不恰当(跨站脚本)
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
Gitea Gitea 1.27.0 ~ 1.27.1 -

II. Public POCs for CVE-2026-60008

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-60008

请登录查看更多情报信息。

Patches & Fixes for CVE-2026-60008 (2)

Vendor Pages for CVE-2026-60008 (1)

Other References for CVE-2026-60008 (1)

Other References for CVE-2026-60008 (1)

Same Patch Batch · Gitea · 2026-10-14 · 36 CVEs total

CVE-2026-68964 Gitea restricted-user SSH and GPG key metadata disclosure
CVE-2026-70396 Gitea organization repository creation token scope bypass
CVE-2026-70406 Gitea private comparison disclosure with public-only tokens
CVE-2026-70400 Gitea private migration creation with public-only tokens
CVE-2026-70402 Gitea local code execution through writable Git hooks
CVE-2026-67577 Gitea restricted-user activity and heatmap disclosure
CVE-2026-63792 Gitea private reusable workflow disclosure to fork runs
CVE-2026-63021 Gitea Swift package manifest memory exhaustion
CVE-2026-62925 Gitea Alpine package parsing memory exhaustion
CVE-2026-70407 Gitea organization listing token scope bypass
CVE-2026-68957 Gitea restricted-user issue search disclosure
CVE-2026-73814 Gitea repository ownership escalation by administrators
CVE-2026-73800 Gitea reusable workflow secret exposure in pull_request_target
CVE-2026-73535 Gitea second-factor bypass through OpenID identity linking
CVE-2026-73804 Gitea API token scope escalation through HTTP signatures
CVE-2026-73539 Gitea external renderer argument injection and code execution
CVE-2026-78231 Gitea blind SSRF through OpenID assertion verification
CVE-2026-78433 Gitea private attachment disclosure through repository mismatch
CVE-2026-73126 Gitea private workflow badge token scope bypass
CVE-2026-73802 Gitea Runner host isolation bypass through container options

Showing top 20 of 36 CVEs. View all on vendor page → →

IV. Related Vulnerabilities

V. Comments for CVE-2026-60008

No comments yet


Leave a comment