Key points
- CVE-2026-110767 affects Gitingest versions up to and including 0.3.1.
- The flaw is rated high severity with a CVSS score of 8.7.
- Attackers can read up to ten megabytes of server files through this issue.
A symlink following vulnerability in Gitingest allows unauthenticated attackers to read server files. The flaw exists in versions up to 0.3.1 and carries a high severity rating.
What happened
The National Vulnerability Database records CVE-2026-110767 as affecting Gitingest through version 0.3.1. The vulnerability stems from how the application handles single-file blob ingestion within the ingest_query function. An unauthenticated attacker can exploit this by submitting a blob URL that points to a symbolic link.
This symlink can be committed to a public repository. When the server processes the URL, it follows the link and returns the content of the target file. The attacker can read any file that the service user has permission to access.
The amount of data an attacker can exfiltrate in a single request is limited to ten megabytes. The weakness is classified under CWE-59, which relates to symlink following vulnerabilities. This means the application trusts the path specified in the symlink without sufficient validation.
Why it matters
Organisations using Gitingest for code ingestion are exposed to unauthorized data access. Because the attack is unauthenticated, any individual with internet access can attempt to exploit the flaw. The ability to read arbitrary files can lead to the exposure of sensitive configuration data or credentials.
The high CVSS score of 8.7 reflects the ease of exploitation and the potential impact on confidentiality. Security teams must verify if their instances are running affected versions. The lack of authentication requirements makes this a significant risk for publicly accessible services.
What happens next
- Identify all instances of Gitingest running version 0.3.1 or lower.
- Monitor logs for unusual blob URL submissions or large file requests.
- Restrict network access to the service if immediate patching is not possible.
- Review file permissions to limit the scope of readable files by the service user.
Patch priority
Teams usually prioritise systems exposed to untrusted external inputs. Check whether your Gitingest instances accept public repository links. If so, isolate these services from sensitive internal networks. Test any configuration changes in a non-production environment first. Back up current settings before making modifications. Reduce exposure by limiting the service user's file read permissions. This containment strategy helps mitigate risk while awaiting vendor guidance.
What to do and how to stay safe: Gitingest
- Audit your environment to locate all deployments of Gitingest version 0.3.1 or earlier.
- Implement network segmentation to restrict access to Gitingest services from untrusted networks.
- Monitor server logs for requests containing symlink references or unusual blob URLs.
- Review the file system permissions of the service account running Gitingest to limit access.
Step-by-step guide: Patch Management: Definition, Purpose and Operational Reality
General security guidance from the AppSec Scoop newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
Which versions of Gitingest are affected by CVE-2026-110767?
Gitingest versions up to and including 0.3.1 are affected by this vulnerability.
What is the CVSS score for this vulnerability?
The CVSS score is 8.7, which is classified as high severity.
Can an attacker execute code through this flaw?
The source material states the flaw allows reading server files, not code execution.
