VulnerabilityPublished 19 Jan 2026Updated 23 Feb 2026

CVE-2026-1175: birkir prime · Information Exposure Through Error Message

Affects birkir primeSource CVE Database V5

Public exploit available · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
birkirprime	Affected =0.4.0.beta	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

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.

Description

A vulnerability was identified in birkir prime up to 0.4.0.beta.0. This impacts an unknown function of the file /graphql of the component GraphQL Directive Handler. Such manipulation leads to information exposure through error message. The attack may be performed from remote. The exploit is publicly available and might be used. The project was informed of the problem early through an issue report but has not responded yet.

Impact

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.

Summary

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. This vulnerability highlights the importance of proper error handling and sanitization in GraphQL APIs to prevent leakage of sensitive internal information.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 22:18 UTC

Technical details

References

Community reviews

Related threats