Bookmarks

    Nothing saved yet. Use the bookmark on any article. Bookmarks are kept on this device only: they stay private and work without an account.

    Settings

    Appearance

    Reading mode

    Font size

    Content width

    Line spacing

    Keyboard shortcuts

    /
    Search
    j k
    Next / previous story
    ← →
    Previous / next section (columns)
    b
    Bookmarks
    s
    Settings
    r
    Columns / scroll
    t
    Light / dark

    Saved in this browser only.

    Ping2Prompt
    Subscribe to the Weekly Brief Sign in
    Ping2Prompt story card: DeepAudit SSRF flaw leaks GitLab and Gitea tokens; no fix yet. High, Gitea.

    DeepAudit SSRF flaw leaks GitLab and Gitea tokens; no fix yet

    Gitea

    DeepAudit SSRF lets registered users capture server tokens

    CVE-2026-129880 is a server-side request forgery (SSRF) flaw in DeepAudit that lets a registered user leak the server-wide GitLab or Gitea token through repository_url. It is rated high: 8.3 on the CVSS 4.0 scale.

    A repository_url pointed at an attacker's host

    The attacker creates a gitlab or gitea project whose repository_url points to a host they control, then requests the project's branches. That captures the operator's token, and it can also reach internal hosts.

    The attack needs only a registered user account. The CVSS vector shows network access, low complexity, low privileges and no user interaction. The NVD references point to backend/app/api/v1/endpoints/projects.py, services/scanner.py and utils/repo_utils.py. The affected area is the project branch listing, which handles repository_url for gitlab and gitea projects.

    DeepAudit 2.0.0-beta.5 through 3.8.0 are affected

    If you run DeepAudit anywhere from 2.0.0-beta.5 through 3.8.0, your instance is in the affected range. According to the NVD, the record's status is still "Received," and it does not state whether attacks have happened, so the exploitation status is unknown. Its references include a VulnCheck advisory and a write-up at vul.yulun.ac.cn.

    No DeepAudit fix is published yet

    The sources name no fixed version, so the table below is empty, and they state no workaround. Watch the DeepAudit project for a newer release and update when one addresses this CVE. Our own suggestion, not vendor guidance: because the attack needs a registered account, limit who holds accounts on your instance. Also treat the server-wide GitLab or Gitea token as possibly exposed and rotate it.

    Sources


    This story was produced with AI assistance from the sources listed above and fact-checked against them before publication. Read our editorial methodology and the corrections log. Spotted an error? Email [email protected].

    Continue

    Share on Bluesky · Mastodon · Email ·

    Discussion