How severe is GHSA-2944-57xv-2682?

No CVSS score has been assigned to GHSA-2944-57xv-2682 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2944-57xv-2682?

GHSA-2944-57xv-2682 affects the following packages: @asymmetric-effort/specifyjs (npm). Ecosystems affected: npm.

How do I fix GHSA-2944-57xv-2682?

Update @asymmetric-effort/specifyjs to 0.2.136 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2944-57xv-2682 is resolved across your whole dependency graph.

How do I detect GHSA-2944-57xv-2682 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @asymmetric-effort/specifyjs. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-2944-57xv-2682 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-2944-57xv-2682?

O3 pinpoints whether GHSA-2944-57xv-2682 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-2944-57xv-2682 actively exploited in the wild?

No public exploit code has been indexed for GHSA-2944-57xv-2682 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-2944-57xv-2682 published, and has it been updated?

GHSA-2944-57xv-2682 was published on July 2, 2026 and was last updated on July 2, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-2944-57xv-2682

Fix: asymmetric-effort/specifyjs@25d1fb4

GHSA-2944-57xv-2682 is a security vulnerability in @asymmetric-effort/specifyjs. O3 Security confirms whether GHSA-2944-57xv-2682 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

@asymmetric-effort/specifyjs: `data:` URI allowed without size restriction

Published

Jul 2, 2026

Updated

Jul 2, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jul 2, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@asymmetric-effort/specifyjsnpm

1Kdownloads / week

Description

Finding

Location: core/src/shared/secure-fetch.ts:33-35

data: URIs were allowed without any restriction. While data: URIs don't make network requests, they can be used for memory exhaustion via very large data URIs.

Status

Fixed in v0.2.136 — data: URIs are now limited to 1MB. URIs exceeding this limit throw an error.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@asymmetric-effort/specifyjs`	all versions	0.2.136

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @asymmetric-effort/specifyjs. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @asymmetric-effort/specifyjs to 0.2.136 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2944-57xv-2682 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-2944-57xv-2682 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-2944-57xv-2682. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Finding **Location**: `core/src/shared/secure-fetch.ts:33-35` `data:` URIs were allowed without any restriction. While `data:` URIs don't make network requests, they can be used for memory exhaustion via very large data URIs. ## Status **Fixed in v0.2.136** — `data:` URIs are now limited to 1MB. URIs exceeding this limit throw an error.

O3 Security · Impact-Aware SCA

Is GHSA-2944-57xv-2682 in your dependencies?

O3 detects GHSA-2944-57xv-2682 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works