Unauthenticated metadata disclosure via GraphQL validation errors
Published Jan 19, 2026 · Updated Jan 19, 2026
Information disclosure in Prime 0.4.0.beta.0 and earlier allows remote attackers to enumerate GraphQL directive metadata via /graphql. The GraphQL Directive Handler returns validation errors for crafted queries that reveal directive names, parameters, and default values. No authentication or user interaction is required, and the disclosed schema details expose security-control metadata rather than application data.
Summary
What happened
Information disclosure in Prime 0.4.0.beta.0 and earlier allows remote attackers to enumerate GraphQL directive metadata via /graphql. The GraphQL Directive Handler returns validation errors for crafted queries that reveal directive names, parameters, and default values. No authentication or user interaction is required, and the disclosed schema details expose security-control metadata rather than application data.
The record
- CVE
- CVE-2026-1175
- Published
- Jan 19, 2026
- Updated
- Jan 19, 2026
- Vendor
- Birkir Gudjonsson
- Product
- Prime
- Classifications
- CWE-209, CWE-200
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 19, 2026CVE publishedPublication date reported by the CVE source.
- Jan 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.4.0.beta
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub issue 546 GraphQL requestproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo