CVE-2026-1173: GraphQL Batch Denial of Service in birkir prime

CVE-2026-1173 is a medium-severity denial of service (CVSS 5.3) in birkir prime up to 0.4.0.beta.0. The array based query batch handler on the /graphql endpoint can be abused remotely to exhaust resources. The record lists no fix and says the project has not responded, so cap batch size and rate limit the endpoint.

What's affected

• Product: birkir prime, versions up to and including 0.4.0.beta.0.
• Vulnerable component: the GraphQL array based query batch handler on /graphql.
• Fixed version: none listed. The record says the project was told early through an issue report and has not responded yet.
• Weakness class: CWE-404 (improper resource shutdown or release).
• Impact: availability only. The vector shows no confidentiality or integrity impact.
• Exploitation: the record says the exploit has been made public. It is not in the CISA Known Exploited Vulnerabilities catalog.

How to check if you're exposed

If prime is installed through npm, a dependency scan can find it in your lockfile.

npm ls --all | grep -i prime

You can also paste your lockfile into the free scan at gold.safeguard.sh/scan. Then check two things:

1. Whether the installed version is 0.4.0.beta.0 or earlier.
2. Whether /graphql is reachable from the internet, and whether your reverse proxy limits request size and request rate on it.

What to do now

1. Limit request body size and request rate on /graphql at the reverse proxy or gateway.
2. If you do not need batched queries, block JSON array bodies on that endpoint at the proxy, or reject them in a gateway rule.
3. Put the endpoint behind authentication or an allowlist where your use case permits.
4. Watch the project issue and the repository for a fix. Do not assume one exists until a release says so.

Why it matters

GraphQL servers often accept an array of queries in one HTTP request. Each entry costs work, so a server that does not bound the number of entries, or the work they trigger, can be made to spend its memory or CPU on a single request. The record classes this as improper resource shutdown or release, and rates the impact as Low on availability only.

A score of 5.3 means the risk is a service outage, not data loss. For a public GraphQL endpoint, an outage is still worth planning for, and the controls that help are generic ones you can apply today: size limits, rate limits and depth or cost limits at the edge.

Quick check

Sources

• Gold entry and CVE record: CVE-2026-1173.
• References listed in the record, not retrievable for this review: project repository, project issue 544 and the VulDB entry.

Last reviewed: 19 October 2026.