VulnerabilityPublished 19 Jan 2026Updated 23 Feb 2026

CVE-2026-1170: birkir prime · Information Disclosure

Affects birkir primeSource CVE Database V5

Public exploit available · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 17:16 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 37% 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

Immediately restrict access to the /graphql endpoint by implementing network-level controls such as IP whitelisting, VPN access, or firewall rules to limit exposure to trusted users only.
Deploy Web Application Firewalls (WAFs) with custom rules to detect and block suspicious or malformed GraphQL queries that could trigger the vulnerability.
Monitor API traffic closely for unusual patterns or spikes in requests to the /graphql endpoint, which may indicate exploitation attempts.
If possible, disable or limit the GraphQL API functionality temporarily until a patch or official fix is released by the birkir project.
Conduct a thorough audit of exposed data via the GraphQL API to understand what information could be leaked and apply data minimization principles.
Engage with the birkir project or community to obtain updates or unofficial patches and contribute to remediation efforts.
Implement strict input validation and query depth limiting on GraphQL queries to reduce the attack surface.
Prepare incident response plans to quickly address any detected exploitation attempts. These steps go beyond generic advice by focusing on immediate containment, traffic monitoring, and proactive API security hardening tailored to the GraphQL context.

Description

A vulnerability was detected in birkir prime up to 0.4.0.beta.0. This issue affects some unknown processing of the file /graphql of the component GraphQL API. Performing a manipulation results in information disclosure. The attack may be initiated remotely. The exploit is now public and may 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-1170 is unauthorized disclosure of sensitive information via the GraphQL API endpoint. This can lead to leakage of confidential data, which may include user information, internal configuration, or other sensitive backend data. Such information disclosure can facilitate further attacks, including targeted phishing, credential theft, or exploitation of other vulnerabilities. Since the vulnerability requires no authentication and can be exploited remotely, any exposed birkir prime GraphQL API endpoint is at risk. Organizations relying on birkir prime for critical applications or handling sensitive data face increased risk of data breaches and compliance violations. The absence of a patch increases the window of exposure, and the public exploit availability raises the likelihood of opportunistic attacks. While the vulnerability does not affect system integrity or availability directly, the confidentiality breach alone can have severe reputational and operational consequences. This threat is particularly impactful for organizations with publicly accessible GraphQL APIs or those lacking network segmentation and strict access controls.

Summary

CVE-2026-1170 is a medium-severity information disclosure vulnerability identified in the birkir prime software, specifically affecting versions up to 0.4.0.beta.0. The vulnerability resides in the processing of the /graphql endpoint of the GraphQL API component. By crafting and sending manipulated requests to this endpoint, an attacker can remotely trigger unintended information disclosure, potentially exposing sensitive data handled by the API. The vulnerability does not require any authentication or user interaction, making it accessible to unauthenticated remote attackers. The CVSS 4.0 vector indicates the attack vector is network-based (AV:N), with low attack complexity (AC:L), no privileges required (PR:N), and no user interaction (UI:N). The impact is limited to confidentiality (VC:L) without affecting integrity or availability. The exploit code is publicly available, increasing the risk of exploitation, although no active exploitation has been reported. The lack of a patch and the public availability of an exploit make this a notable risk for organizations using birkir prime, especially those exposing the GraphQL API endpoint to untrusted networks. Given the nature of GraphQL APIs, attackers could leverage this vulnerability to extract sensitive information such as user data, configuration details, or other backend information that should remain confidential. The vulnerability highlights the importance of secure API design and input validation in GraphQL implementations.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats