# CVE-2026-78497: JQ::Lite versions before 2.51 for Perl execute Perl code embedded in a query's regular expression by compiling it with string eval.

> Attackers can execute arbitrary Perl code by injecting code blocks into regular expressions within JQ::Lite queries.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Oct 2026
- **Updated:** 20 Oct 2026

## What is CVE-2026-78497?

CVE-2026-78497 is a high-severity code injection vulnerability, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

JQ::Lite versions before 2.51 for Perl execute Perl code embedded in a query's regular expression by compiling it with string eval.

The pattern given to test(), match(), or the match and =~ conditions of select() is placed in a `qr'...'` literal and compiled as source text, so a `(?{ ... })` code block in it runs without `use re 'eval'`. Single quotes in the pattern are escaped, but a code block runs in place and needs none.

An attacker who supplies a query, or text that an application inserts into the pattern of one, can execute arbitrary Perl code in the calling process.

Weakness: CWE-95 (Improper Neutralization of Directives in Dynamically Evaluated Code)

## Which versions are affected by CVE-2026-78497?


## How do I fix CVE-2026-78497?

No fix has been published for CVE-2026-78497 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-78497 being exploited?

There is no known exploitation of CVE-2026-78497 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-78497 and fix it if it is affected.

What it is: CVE-2026-78497 is a high-severity code injection vulnerability, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-78497 in the wild and no public exploit code.

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/CVE-2026-78497/ (Markdown: https://insights.sbomify.com/CVE-2026-78497/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-78497
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-78497
- OSV: https://osv.dev/vulnerability/CVE-2026-78497

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-78497/
Summaries are generated and may contain mistakes; the official description above is the record.