CVE-2026-1175 identifies an information exposure vulnerability in the birkir prime software, versions up to 0.4.0.beta.0. The vulnerability resides in an unspecified function within the GraphQL Directive Handler component, specifically at the /graphql endpoint. When manipulated by a remote attacker, this flaw causes the application to return error messages that inadvertently disclose sensitive information about the internal workings or configuration of the system. Such information leakage can include stack traces, database schema details, or other debugging data that can facilitate further exploitation or reconnaissance. The vulnerability requires no authentication or user interaction and can be triggered remotely over the network, increasing its risk profile. The CVSS 4.0 base score is 6.9 (medium severity), reflecting the ease of exploitation and the limited scope of impact confined to information disclosure without direct integrity or availability compromise. The exploit code is publicly available, increasing the likelihood of opportunistic scanning and exploitation attempts. Despite early notification to the birkir project, no patch or official response has been issued, leaving users exposed. This vulnerability highlights the importance of proper error handling and sanitization in GraphQL APIs to prevent leakage of sensitive internal information.

The primary impact of CVE-2026-1175 is the unauthorized disclosure of sensitive internal information through error messages. This can aid attackers in gaining insights into the application’s architecture, database schema, or other backend details, which can be leveraged to craft more effective attacks such as injection, authentication bypass, or privilege escalation. While the vulnerability does not directly compromise data integrity or availability, the information exposure increases the overall attack surface and risk profile of affected systems. Organizations running birkir prime in vulnerable versions may face increased reconnaissance activity and targeted attacks. In environments where sensitive or regulated data is processed, even indirect information leakage can have compliance and reputational consequences. The lack of vendor response and patch availability prolongs exposure and complicates risk management efforts.

To mitigate CVE-2026-1175, organizations should first assess their use of birkir prime and identify any deployments running version 0.4.0.beta.0 or earlier. Until an official patch is released, implement the following specific measures: 1) Configure the GraphQL server to suppress detailed error messages in production environments, ensuring that only generic error responses are returned to clients. 2) Employ Web Application Firewalls (WAFs) with rules to detect and block suspicious requests targeting the /graphql endpoint that may trigger error conditions. 3) Conduct thorough input validation and sanitization on all GraphQL queries and directives to reduce the chance of error-triggering malformed inputs. 4) Monitor logs and network traffic for unusual or repeated error-inducing requests that could indicate exploitation attempts. 5) Engage with the birkir project community or maintainers to track patch releases or updates addressing this vulnerability. 6) Consider isolating or restricting access to the /graphql endpoint to trusted networks or authenticated users where feasible to reduce exposure. These targeted actions go beyond generic advice by focusing on error handling, monitoring, and access control specific to the vulnerable component.