dbcve.org
Developer HubApplication · Redhat

CVE-2026-3118

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
A security flaw was identified in the Orchestrator Plugin of Red Hat Developer Hub (Backstage). The issue occurs due to insufficient input validation in GraphQL query handling. An authenticated user can inject specially crafted input into API requests, which disrupts backend query processing. This results in the entire Backstage application crashing and restarting, leading to a platform-wide Denial of Service (DoS). As a result, legitimate users temporarily lose access to the platform.

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 confidence

The Orchestrator Plugin in Red Hat Developer Hub (Backstage) contains an input validation flaw in its GraphQL query handling. An authenticated attacker can inject specially crafted malicious input into API requests, causing backend query processing to fail catastrophically. This triggers a complete application crash and restart, resulting in platform-wide Denial of Service.

MitigationImplement robust input validation and sanitization for all GraphQL queries in the Orchestrator Plugin, along with proper error handling to prevent application crashes. Consider adding rate limiting and query complexity analysis to mitigate DoS risks.

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
Developer HubApplication
Affected:all versions

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Red Hat Developer Hub is installed
    Identify the RHDH installation and note the version if accessible. Check for presence of @backstage-community/plugin-orchestrator or similar orchestrator package in the codebase or node_modules.
    Affected if Red Hat Developer Hub is running with the Orchestrator Plugin enabled
  2. Verify Orchestrator Plugin is enabled
    Check the RHDH app-config.yaml or app-config.local.yaml for entries referencing 'orchestrator' under the plugins or catalog configuration sections.
    Affected if The Orchestrator Plugin is listed as an installed/enabled plugin in the configuration
  3. Confirm GraphQL endpoint exposure
    Inspect the RHDH backend API routes to identify if /api/orchestrator/graphql or similar GraphQL endpoints are exposed. Check the main router configuration for orchestrator-related route definitions.
    Affected if GraphQL endpoints for the Orchestrator Plugin are accessible via the API gateway
  4. Review application logs for crash patterns
    Examine RHDH backend logs for entries indicating GraphQL query processing failures, uncaught exceptions, or application restart events occurring after GraphQL requests.
    Affected if Recent logs show correlation between GraphQL API calls and application crash/restart events

If RHDH is running with the Orchestrator Plugin enabled and its GraphQL endpoints are exposed, the environment is affected by this vulnerability since all versions are impacted.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement robust input validation and sanitization for all GraphQL queries in the Orchestrator Plugin, along with proper error handling to prevent application crashes. Consider adding rate limiting and query complexity analysis to mitigate DoS risks.

Recommended fix Moderate confidence

Latest Red Hat Developer Hub release with CVE-2026-3118 patch (check access.redhat.com for exact version)

  1. Check Red Hat Developer Hub release notes and security advisories on access.redhat.com for the latest patched version addressing CVE-2026-3118
  2. Identify the Orchestrator Plugin version currently in use within your Red Hat Developer Hub installation
  3. Upgrade Red Hat Developer Hub to the latest version that includes the security fix for the Orchestrator Plugin SQL injection vulnerability
  4. After upgrading, verify that the Orchestrator Plugin is functioning correctly and the GraphQL API endpoints are operational
  5. Monitor the application logs to confirm no SQL injection attempts are occurring and the DoS condition is resolved
Caveat Review release notes for any breaking changes in the Orchestrator Plugin or GraphQL API changes between your current version and the upgrade target

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Developer Hub Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3118 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3118 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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