Summary
@asymmetric-effort/specifyjs: Production console warnings may leak internal framework state
Finding
Location: core/src/core/scheduler.ts:23, core/src/hooks/dispatcher.ts:100, core/src/client/graphql.ts:71
Several console.warn calls are not gated behind __DEV__ and will fire in production builds, potentially exposing internal framework state such as queue sizes, component names, and query fragments to users viewing the browser console.
Status
Open, These warnings serve as development-time diagnostics. They do not expose credentials or PII, but may reveal internal architecture details.
Impact
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Gate all development-time console.warn and console.error calls behind process.env.NODE_ENV !== 'production' or a __DEV__ constant that build tools can tree-shake.
Frequently Asked Questions
- What is GHSA-QCR8-X557-7CP3? GHSA-QCR8-X557-7CP3 is a medium-severity security vulnerability in @asymmetric-effort/specifyjs (npm), affecting versions <= 0.2.137. It is fixed in 0.2.140.
- Which versions of @asymmetric-effort/specifyjs are affected by GHSA-QCR8-X557-7CP3? @asymmetric-effort/specifyjs (npm) versions <= 0.2.137 is affected.
- Is there a fix for GHSA-QCR8-X557-7CP3? Yes. GHSA-QCR8-X557-7CP3 is fixed in 0.2.140. Upgrade to this version or later.
- Is GHSA-QCR8-X557-7CP3 exploitable, and should I be worried? Whether GHSA-QCR8-X557-7CP3 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-QCR8-X557-7CP3 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-QCR8-X557-7CP3? Upgrade
@asymmetric-effort/specifyjsto 0.2.140 or later.