CVE-2026-1171

5.3 MEDIUM

📋 TL;DR

This vulnerability in birkir prime's GraphQL Field Handler allows remote attackers to cause denial of service through manipulation of the /graphql endpoint. Systems running birkir prime up to version 0.4.0.beta.0 are affected. The exploit has been published and may be actively used against vulnerable installations.

💻 Affected Systems

Products:
  • birkir prime
Versions: Up to and including 0.4.0.beta.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects systems with GraphQL endpoint enabled and accessible

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete service unavailability requiring system restart or recovery procedures

🟠

Likely Case

Temporary service disruption affecting GraphQL functionality

🟢

If Mitigated

Minimal impact with proper rate limiting and request validation

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Exploit details published in GitHub issue #542, remote attack vector confirmed

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Not available

Vendor Advisory: Not available

Restart Required: No

Instructions:

No official patch available. Monitor GitHub repository for updates: https://github.com/birkir/prime

🔧 Temporary Workarounds

Implement GraphQL Query Depth Limiting

all

Limit maximum query depth to prevent complex queries that could trigger the DoS

# Implementation depends on your GraphQL server setup

Add Rate Limiting to /graphql Endpoint

all

Implement request rate limiting to prevent abuse

# Use web server or application-level rate limiting

🧯 If You Can't Patch

  • Restrict network access to GraphQL endpoint using firewall rules
  • Implement Web Application Firewall (WAF) with GraphQL attack detection rules

🔍 How to Verify

Check if Vulnerable:

Check if running birkir prime version <= 0.4.0.beta.0 and GraphQL endpoint is accessible

Check Version:

Check package.json or application configuration for version

Verify Fix Applied:

Verify version is > 0.4.0.beta.0 when patch becomes available

📡 Detection & Monitoring

Log Indicators:

  • Unusually large GraphQL queries
  • Multiple failed GraphQL requests from single source
  • High CPU/memory usage spikes

Network Indicators:

  • High volume of requests to /graphql endpoint
  • Abnormal GraphQL query patterns

SIEM Query:

source="web_logs" AND uri_path="/graphql" AND (request_size>10000 OR status_code=500)

🔗 References

📤 Share & Export