CVE-2026-1173
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability was found in birkir prime up to 0.4.0.beta.0. The impacted element is an unknown function of the file /graphql of the component GraphQL Array Based Query Batch Handler. The manipulation results in denial of service. The attack can be executed remotely. The exploit has been made public and could be used. The project was informed of the problem early through an issue report but has not responded yet.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA denial of service vulnerability exists in birkir prime (up to 0.4.0.beta.0) within the GraphQL Array Based Query Batch Handler component at the /graphql endpoint. The vulnerability involves an unknown function that can be exploited remotely to cause DoS, and a public exploit is available.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 0.4.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify birkir prime installationLocate the application running in your environment that uses the birkir prime software package. Check your application inventory, container registry, or deployment manifests for references to birkir prime.Affected if birkir prime is present in your environment
-
Check birkir prime versionIdentify the installed version of birkir prime by examining your package.json, requirements.txt, Gemfile, or equivalent dependency file. Also check the running application's About page, headers, or API version endpoint if available.Affected if the installed version is 0.4.0 or any version up to and including 0.4.0.beta.0
-
Confirm GraphQL endpoint exposureAttempt to access the /graphql endpoint on your birkir prime server by sending a POST request to http(s)://yourserver/graphql with a valid GraphQL query or introspection query. Also check your web server logs for requests to this path.Affected if the /graphql endpoint is accessible and responds to requests
-
Verify Array Based Query Batch Handler is activeSend a GraphQL batch query (multiple operations in a single array) to the /graphql endpoint. Observe if the endpoint accepts and processes array-based batch requests. Check if your GraphQL configuration enables batch query handling.Affected if the /graphql endpoint accepts and processes array-based batch queries
You are affected if birkir prime version 0.4.0 or lower is running and the /graphql endpoint with its Array Based Query Batch Handler is exposed and functional.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement GraphQL query complexity analysis, depth limiting, and request rate limiting on the /graphql endpoint to mitigate DoS. Consider request timeouts and batching restrictions until the vendor releases a patch.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1173 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-1173 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data