Is This vulnerability exploited in the wild?

No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.

How severe is This vulnerability?

Medium severity, with a CVSS score of 4, published 2 July 2026.

Which products and versions are affected?

@asymmetric-effort/specifyjs (npm) SEMVER:introduced=0,fixed=0.2.140.

Is there a fix for This vulnerability?

Yes. @asymmetric-effort/specifyjs (npm): upgrade to 0.2.140 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is This vulnerability attacked?

It is attacked over the network, in a software library.

Check whether you run @asymmetric-effort/specifyjs (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

@asymmetric-effort/specifyjs information disclosure via console warnings

Severity: medium · CVSS 4 · Published 2026-07-02

@asymmetric-effort/specifyjs is a JavaScript framework used for building component-based applications. Development debugging console warnings intended for developers are being output in production builds, potentially revealing internal architecture details such as queue sizes and component names to end users viewing the browser console. While this does not expose credentials or personal information, it provides attackers reconnaissance information about the application's internal structure.

Technologies: @asymmetric-effort/specifyjs (npm). Vendors: npm.

Quick answers

Is This vulnerability exploited in the wild?: No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?: Medium severity, with a CVSS score of 4, published 2 July 2026.
Which products and versions are affected?: @asymmetric-effort/specifyjs (npm) SEMVER:introduced=0,fixed=0.2.140.
Is there a fix for This vulnerability?: Yes. @asymmetric-effort/specifyjs (npm): upgrade to 0.2.140 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is This vulnerability attacked?: It is attacked over the network, in a software library.
Am I affected?: Check whether you run @asymmetric-effort/specifyjs (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

@asymmetric-effort/specifyjs (npm): upgrade to 0.2.140 or later
```
npm install @asymmetric-effort/specifyjs@0.2.140
```

Technical details

This vulnerability is classified as CWE-209 (Generation of Error Message Containing Sensitive Information). The root cause is that multiple console.warn() and console.error() calls in core/src/core/scheduler.ts, core/src/hooks/dispatcher.ts, and core/src/shared/warnings.ts are not gated behind a NODE_ENV or __DEV__ check, causing them to execute in production builds. The attack vector is network-based and requires no authentication—an attacker simply views the browser developer console to observe queue sizes, component names, and query fragments. The fix, available in version 0.2.139, gates all development-time console output behind NODE_ENV !== 'production' checks while preserving the actual queue trimming behavior.

Affected products

asymmetric-effort @asymmetric-effort/specifyjs < 0.2.139

Timeline

2026-05-29: disclosed
2026-05-29: patched: Fixed in v0.2.139

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.