# GHSA-5c7w-4wm3-85vw: @asymmetric-effort/specifyjs: GraphQL gql tag allows metacharacter injection

> An attacker can inject GraphQL metacharacters via interpolated values in the gql tag, potentially executing arbitrary queries or accessing data.

- **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-5c7w-4wm3-85vw?

GHSA-5c7w-4wm3-85vw is a code injection 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/client/graphql.ts:66-80`

The `gql` template tag function warned about interpolated values containing GraphQL metacharacters (`{}():`) but still concatenated them into the query string, enabling potential GraphQL injection.

## Status

**Fixed in v0.2.136** — The `gql` function now throws an error when metacharacters are detected in interpolated values, forcing developers to use the `variables` parameter.

## Which versions are affected by GHSA-5c7w-4wm3-85vw?

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.136 |
| `@asymmetric-effort/specifyjs` | npm | All versions | 0.2.136 |

## How do I fix GHSA-5c7w-4wm3-85vw?

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

## Is GHSA-5c7w-4wm3-85vw being exploited?

There is no known exploitation of GHSA-5c7w-4wm3-85vw in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-5c7w-4wm3-85vw and fix it if it is affected.

What it is: GHSA-5c7w-4wm3-85vw is a code injection 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-5c7w-4wm3-85vw in the wild and no public exploit code.

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

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-5c7w-4wm3-85vw/ (Markdown: https://insights.sbomify.com/GHSA-5c7w-4wm3-85vw/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-5c7w-4wm3-85vw

---
From sbomify Insights: https://insights.sbomify.com/GHSA-5c7w-4wm3-85vw/
Summaries are generated and may contain mistakes; the official description above is the record.