CVE-2026-1172: 
NixOS vulnerability analysis and mitigation

CVE-2026-1172 is a denial-of-service (DoS) vulnerability in birkir/prime, an open-source self-hosted headless GraphQL CMS. The flaw resides in the GraphQL Directive Handler component at the /graphql endpoint and is triggered by GraphQL directive overloading — applying the same directive repeatedly in a single query to exhaust server resources. All versions up to and including 0.4.0.beta.0 are affected. The vulnerability was disclosed publicly on January 19, 2026, with a proof-of-concept exploit available at the time of disclosure. CVSS v3.1 base score is 7.5 (High) per NVD, while the CNA (VulDB) rates it 5.3 (Medium); CVSS v4.0 is rated 5.5 (Medium) (GitHub Issue, Red Hat CVE).

The root cause is classified as CWE-404 (Improper Resource Shutdown or Release), stemming from the GraphQL server's failure to limit the number of times a directive can be applied to a single field in a query. GraphQL's specification permits applying the same directive multiple times at the same location, and the server executes the corresponding processing logic for each instance — leading to resource exhaustion. An unauthenticated remote attacker can send a crafted HTTP POST request to the /graphql endpoint with a query containing a large number of repeated directives (e.g., query cop { __typename @aa@aa@aa@aa@aa@aa@aa@aa@aa@aa }), causing the server to exhaust computing resources and become unresponsive. No authentication, special privileges, or user interaction is required, and attack complexity is low (GitHub Issue, Red Hat CVE).

Successful exploitation results in a complete loss of availability for the affected GraphQL CMS endpoint, effectively taking the service offline for legitimate users. There is no confidentiality or integrity impact — the vulnerability is purely a denial-of-service condition. Because prime is a headless CMS serving content via GraphQL, a sustained attack could disrupt all content delivery and administrative operations dependent on the /graphql endpoint (GitHub Issue, Red Hat CVE).

A public proof-of-concept exploit was disclosed via a GitHub issue report on January 3, 2026, prior to the CVE being formally published on January 19, 2026. The PoC is a simple curl command requiring no authentication, making exploitation trivial. There is no evidence of active in-the-wild exploitation at this time, and no threat actor attribution has been reported. The EPSS score is approximately 0.039%, indicating a low (but non-zero) probability of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. CVSS v4.0 exploit maturity is rated Proof of Concept (GitHub Issue, Red Hat CVE).

1. Reconnaissance: Identify publicly accessible instances of birkir/prime (version ≤ 0.4.0.beta.0) by searching for exposed /graphql endpoints using tools like Shodan, Censys, or by directly probing known deployment URLs.
2. Craft the malicious GraphQL query: Construct a GraphQL query that applies the same directive repeatedly to a single field, e.g., query cop { __typename @aa@aa@aa@aa@aa@aa@aa@aa@aa@aa }. The number of repeated directives can be increased to amplify resource consumption.
3. Send the exploit request: Deliver the payload via an HTTP POST request to the /graphql endpoint:

   curl -X POST -H "Content-Type: application/json" \
     -d '{"query": "query cop { __typename @aa@aa@aa@aa@aa@aa@aa@aa@aa@aa }", "operationName": "cop"}' \
     'http://<target>/graphql'

4. Repeat to sustain DoS: Send the request repeatedly or in parallel to maintain resource exhaustion and keep the service unavailable to legitimate users.
5. Observe impact: The GraphQL server becomes unresponsive or crashes due to exhausted computing resources, denying service to all users of the CMS (GitHub Issue).

• Network: High volume of HTTP POST requests to /graphql from a single or small set of source IPs; requests with unusually large or repetitive query field values in the JSON body; repeated requests with User-Agent: oxpecker (as seen in the public PoC).
• Logs: Web server or application logs showing a spike in POST requests to /graphql with query strings containing repeated @ directive patterns (e.g., @aa@aa@aa@aa); elevated error rates or timeout responses from the GraphQL handler.
• Process/Application: Sudden spike in CPU or memory utilization by the Node.js/prime process; application becoming unresponsive or crashing; increased garbage collection activity or out-of-memory errors in application logs (GitHub Issue).

Upgrade birkir/prime to a version beyond 0.4.0.beta.0 once a patched release is available; the vendor has been notified but had not responded as of the disclosure date. As an interim workaround, restrict network access to the /graphql endpoint using firewall rules or API gateway policies to limit exposure to trusted clients only. Additionally, implement rate limiting and request validation (e.g., maximum query depth/complexity limits, directive count limits) at the reverse proxy or WAF layer to block malformed or abusive GraphQL queries. Monitor the /graphql endpoint for anomalous request patterns indicative of directive overloading (GitHub Issue, Red Hat CVE).

The vulnerability was reported by researcher NinjaGPT via a GitHub issue on January 3, 2026, with a working PoC included. The project maintainer had not responded to the issue as of the disclosure date, which was noted in the CVE description. A security advisory was subsequently published by zast.ai covering this and other unpatched vulnerabilities in the Prime CMS GraphQL implementation (zast.ai Advisory). Coverage was also picked up by automated vulnerability tracking services including VulDB, INCIBE-CERT, and Radar by Offseq.