CVE-2026-1169
Unknown Unknown - Not Provided
Cross-Site Request Forgery in Birkir Prime ≤ 0.4.0.beta

Publication date: 2026-01-19

Last updated on: 2026-04-29

Assigner: VulDB

Description
A security vulnerability has been detected in birkir prime up to 0.4.0.beta.0. This vulnerability affects unknown code. Such manipulation leads to cross-site request forgery. The attack can be launched remotely. The exploit has been disclosed publicly and may be used. The project was informed of the problem early through an issue report but has not responded yet.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-01-19
Last Modified
2026-04-29
Generated
2026-06-16
AI Q&A
2026-01-19
EPSS Evaluated
2026-06-15
NVD
CVE-2026-1169
EUVD
EUVD-2026-3205
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
unknown_vendor birkir_prime to 0.4.0.beta.0 (inc)
birkir prime to 0.4.0 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-862 The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
CWE-352 The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

CVE-2026-1169 is a Cross-Site Request Forgery (CSRF) vulnerability in birkir prime versions up to 0.4.0.beta.0. It arises because the GraphQL implementation allows client queries via HTTP GET requests without proper CSRF protections. Attackers can craft malicious GET requests that execute unauthorized actions on behalf of privileged users without their consent. This means an attacker can trick a user into executing unwanted actions remotely by exploiting the way the application handles these GET requests. [1, 2, 3]

Impact Analysis

This vulnerability can allow attackers to perform unauthorized actions on your behalf if you are a privileged user of birkir prime. Since the exploit can be launched remotely and does not require authentication, attackers can trick users into executing malicious requests that compromise the integrity of the system. This can lead to manipulation of data or actions within the application without the user's knowledge or consent. The exploit is easy to perform and publicly available, increasing the risk of exploitation. [1, 2, 3]

Detection Guidance

This vulnerability can be detected by monitoring for suspicious HTTP GET requests containing GraphQL query parameters sent to the birkir prime application endpoints. A practical detection method is to look for unusual or unauthorized GET requests that include GraphQL queries, which may indicate exploitation attempts. A suggested command to test or detect the vulnerability is using curl to send a crafted GET request with a GraphQL query parameter to the target endpoint, for example: curl -G 'http://target/endpoint' --data-urlencode 'query={maliciousQuery}'. Monitoring logs for such requests can help identify potential exploitation. [2]

Mitigation Strategies

Immediate mitigation steps include disabling or restricting the use of HTTP GET requests for GraphQL queries in birkir prime, as this is the root cause enabling CSRF attacks. Since the project maintainers have not provided any fixes or countermeasures yet, consider implementing CSRF protections such as requiring anti-CSRF tokens or switching to POST requests for GraphQL queries. If mitigation is not feasible, consider replacing the affected product with an alternative that does not have this vulnerability. [3]

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-1169. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart