Gitingest CVE-2026-110767

The target Gitingest instance (version ≤0.3.1) must be network-reachable and must accept attacker-supplied repository/blob URLs for ingestion - which is the default operating mode of both the hosted service and self-hosted deployments. The specific trigger is the single-file blob ingestion path in ingest_query, which follows a symbolic link committed to a public repository rather than restricting reads to in-repo content. No authentication, credentials, or user interaction are required (PR:N/UI:N). Limiting factors: disclosure is bounded to files the service account can read and capped at 10 MB per request, exploitation requires the attacker to host the malicious symlink in a reachable public repo, and risk is confined to instances exposed to untrusted submitters - an internal-only instance behind access controls is far less exposed.

This is a credible, actionable priority rather than a high-CVSS paper tiger. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) describes network-reachable, low-complexity, fully unauthenticated exploitation with no user interaction, and the impact profile (VC:H, VI:N, VA:N) correctly reflects a pure confidentiality/arbitrary-file-read flaw (CWE-59 symlink following) with no integrity or availability impact. The signals are internally consistent: the description matches the vector - any anonymous user who can submit a repository blob URL to a Gitingest instance can read files the service account can access (up to 10 MB). No conflict exists between the vector and the description. The limiting factor on real-world blast radius is exposure: the risk is acute for the public hosted service and any internet-reachable self-hosted instance, but low for instances not exposed to untrusted submitters. Missing/absent signals should temper urgency ranking: there is no EPSS score, no CISA KEV listing, and no explicit POC flag in the input, so 'actively exploited' cannot be asserted. However, a detailed public technical writeup (hackmd) and a VulnCheck advisory exist, meaning the exploitation technique is fully disclosed and low-effort to reproduce - treat weaponization as imminent even though active exploitation is unconfirmed.

An attacker creates or forks a public Git repository and commits a symbolic link pointing to a sensitive server path (e.g., /etc/passwd, application config, or cloud credential files). They then submit the blob URL of that symlink to an exposed Gitingest instance; the single-file blob ingestion path in ingest_query follows the link and returns the target file's contents. Because the CVSS vector is AV:N/AC:L/PR:N/UI:N, this requires no authentication, no user interaction, and only a single crafted request against a default-reachable instance; a public technical writeup detailing the method already exists.