Security readout for executives and security teams
Plain-English summary
CVE-2026-1172 is a denial-of-service issue in birkir prime’s GraphQL directive handling. A remote attacker may be able to disrupt service availability through the /graphql endpoint. Public exploit information is disclosed, but the provided sources do not show confirmed active exploitation. Urgency depends on whether this beta software is deployed and reachable.
Executive priority
Treat as a targeted availability risk. Prioritize quickly if birkir prime supports business-critical services or exposes /graphql to the internet. If not deployed, no emergency action is needed beyond confirming absence and monitoring for vendor updates.
Technical view
The issue affects birkir prime up to 0.4.0.beta.0 in the GraphQL Directive Handler at /graphql. It is classified as CWE-404 with CVSS 4.0 score 6.9. The vector indicates network exploitation, low complexity, no privileges, no user interaction, and low availability impact. No vendor fix is named in the supplied sources.
Likely exposure
Exposure is likely limited to organizations running birkir prime 0.4.0.beta.0 or earlier, especially where /graphql is reachable from untrusted networks. Because this appears to involve beta software, confirm actual deployment before prioritizing broad response.
Exploitation context
The sources state remote exploitation is possible and public exploit information has been disclosed. The CVE is not listed as KEV, and no supplied source confirms active exploitation in the wild. The documented impact is denial of service, not data theft or code execution.
Researcher notes
Evidence is limited. VulDB reports public disclosure and non-response from the project, but no patch, workaround, or active exploitation evidence is provided. Avoid assuming broader GraphQL product impact; the affected product named in sources is birkir prime.
Mitigation direction
- Inventory birkir prime deployments and identify versions at or below 0.4.0.beta.0.
- Check the GitHub project, CVE record, and VulDB entry for vendor updates.
- Restrict /graphql access to trusted networks or authenticated gateways where feasible.
- Apply API gateway rate limiting and GraphQL request controls if already available.
- Monitor /graphql latency, errors, resource spikes, and unusual request patterns.
- Consider isolating or disabling affected beta deployments until vendor guidance is available.
Validation and detection
- Confirm whether birkir prime is present in application inventories and dependency manifests.
- Verify deployed birkir prime versions against the affected version range.
- Determine whether /graphql is exposed internally, externally, or through an API gateway.
- Review logs for availability issues involving the GraphQL endpoint.
- Track the GitHub issue for maintainer response or remediation details.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-404: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-1172 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.9 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
6.9MediumVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P
Source materials
- CVE List V5 sourceCVE List V5
- VDB-341766 | birkir prime GraphQL Directive graphql denial of serviceCVE reference · vdb-entry, technical-description
- VDB-341766 | CTI Indicators (IOB, IOC, TTP, IOA)CVE reference · signature, permissions-required
- Submit #731103 | birkir prime <=0.4.0 Graphql Directive Overloading VulnerabilityCVE reference · third-party-advisory
- https://github.com/birkir/prime/issues/543CVE reference · exploit, issue-tracking
- https://github.com/birkir/prime/CVE reference · product
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Resource Shutdown or Release
Improper Resource Shutdown or Release represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.