Skip to main content

CVE-2026-78497: CWE-95 Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection')

0
High
VulnerabilityCVE-2026-78497cvecve-2026-78497cwe-95
Published: 10/18/2026 (10/18/2026, 11:32:05 UTC)
Source: CVE Database V5

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.

Affected software

GitHub Actionsmore threats →cve
JQ-Lite
pkg:github/JQ-Lite
Affected versions
>=0 <2.51

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/18/2026, 12:03:40 UTC

Technical Analysis

JQ::Lite versions prior to 2.51 for Perl execute embedded Perl code within query regular expressions by compiling them with string eval. The vulnerability arises because the pattern given to test(), match(), or select() conditions is placed inside a qr'...' literal and compiled as source text, allowing (?{ ... }) code blocks to run without the use of 're eval'. Although single quotes in the pattern are escaped, the code block itself executes directly. This improper neutralization of directives in dynamically evaluated code (CWE-95) enables an attacker who controls the query or inserted text to execute arbitrary Perl code within the calling process.

Potential Impact

An attacker who can supply or influence the query or text inserted into the pattern can execute arbitrary Perl code in the process running JQ::Lite. This can lead to full compromise of the affected application environment, including unauthorized code execution and potential system control.

Mitigation Recommendations

No official patch or fix is currently documented. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, avoid using untrusted input in query patterns or sanitize inputs rigorously to prevent injection of code blocks.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
CPANSec
Date Reserved
2026-08-24T17:17:51.029Z
State
PUBLISHED

Threat ID: 6ad4b23c2cdf04f65664e4c6

Added to database: 10/18/2026, 11:49:16 UTC

Last enriched: 10/18/2026, 12:03:40 UTC

Last updated: 10/18/2026, 19:03:29 UTC

Views: 8

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses