# GHSA-qcr8-x557-7cp3: @asymmetric-effort/specifyjs: Production console warnings may leak internal framework state

> Production console warnings in specifyjs leak internal framework state like queue sizes and component names to users.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Jul 2026

## What is GHSA-qcr8-x557-7cp3?

GHSA-qcr8-x557-7cp3 is a vulnerability in @asymmetric-effort/specifyjs, published on 2 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

## 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.

## Recommendation

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.

## Which versions are affected by GHSA-qcr8-x557-7cp3?

2 open source packages ship an affected version, including @asymmetric-effort/specifyjs.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@asymmetric-effort/specifyjs` | npm | All versions | 0.2.140 |
| `@asymmetric-effort/specifyjs` | npm | All versions | 0.2.140 |

## How do I fix GHSA-qcr8-x557-7cp3?

Upgrade @asymmetric-effort/specifyjs to 0.2.140 or later.

## Is GHSA-qcr8-x557-7cp3 being exploited?

There is no known exploitation of GHSA-qcr8-x557-7cp3 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-qcr8-x557-7cp3 and fix it if it is affected.

What it is: GHSA-qcr8-x557-7cp3 is a vulnerability in @asymmetric-effort/specifyjs, published on 2 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-qcr8-x557-7cp3 in the wild and no public exploit code.

Affected packages and fixed versions:
- @asymmetric-effort/specifyjs (npm): affected all versions; fixed in 0.2.140
- @asymmetric-effort/specifyjs (npm): affected all versions; fixed in 0.2.140

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-qcr8-x557-7cp3/ (Markdown: https://insights.sbomify.com/GHSA-qcr8-x557-7cp3/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-qcr8-x557-7cp3

---
From sbomify Insights: https://insights.sbomify.com/GHSA-qcr8-x557-7cp3/
Summaries are generated and may contain mistakes; the official description above is the record.