Huginn information disclosure in JqAgent via jq env builtin
Only affects Huginn before 2026.11.09 when jq support is enabled through USE_JQ. Fixed in 2026.11.09.
- Exploited
- No known exploitation
- Fix
- Fixed in 2026.11.09
- Who is exposed
- Specific setups only
Summary
Huginn, before the fixed release, has an information exposure flaw in its JqAgent that lets a logged-in user read the server's process environment remotely, because the jq child process inherits it. An attacker who can create, configure, or dry-run a JqAgent can use the env or $ENV filter to reveal secrets such as APP_SECRET_TOKEN and database, SMTP, and OAuth credentials.
Written by a model
Original description
Huginn before 2026.11.09 contains an information exposure vulnerability in JqAgent that allows authenticated users to read the server process environment because the jq child process inherits it. Attackers who can create, configure or dry-run a JqAgent can supply a filter using env or $ENV to disclose APP_SECRET_TOKEN, database, SMTP and OAuth secrets.
Who should check
Teams running Huginn with JqAgent enabled through USE_JQ, where users can create, configure or dry-run JqAgents.
“On installations with JqAgent enabled through USE_JQ”
What to do
Check whether your setup matches what the bug needs.
JqAgent enabled through USE_JQ Huginn versions before v2026.11.09 (all versions up to git 86a924f)Upgrade to a fixed version: 2026.11.09.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-127082 (Huginn before 2026.11.09 Information Exposure via JqAgent jq env Builtin), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-127082 (entry last updated 2026-11-18):
Affected:
- huginn huginn: fixed in 2026.11.09
Fixed versions: 2026.11.09.
Conditions (all must be true for the bug to be hit):
- JqAgent enabled through USE_JQ (source: https://github.com/huginn/huginn/security/advisories/GHSA-3f56-748g-q34j)
- Huginn versions before v2026.11.09 (all versions up to git 86a924f) (source: https://github.com/huginn/huginn/security/advisories/GHSA-3f56-748g-q34j)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-127082 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-127082 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/huginn/huginn/security/advisories/GHSA-3f56-748g-q34j
- https://github.com/huginn/huginn/commit/826f4bd471c027660b1951408b44f9e5c5452aff
- https://github.com/huginn/huginn/blob/v2026.11.05.2/app/models/agents/jq_agent.rb#L166
- https://github.com/huginn/huginn/releases/tag/v2026.11.09
- https://www.vulncheck.com/advisories/huginn-before-2026.11.09-information-exposure-via-jqagent-jq-env-builtin
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-127082
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-127082"}.Affected versions
- huginn huginnfixed in 2026.11.09
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.3/10CVSS 8.3
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now5 days
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Public exploit activity
- EPSS: 0.43%
Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.
Evidence 7
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · huginn/huginn · Advisory GHSA-3f56-748g-q34j |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-127082 |
| Record | NVD · CVE-2026-127082 |
| Other links 4 | |
| Patch | GitHub · huginn/huginn · Commit 826f4bd4 |
| Repository | GitHub · huginn/huginn · app/models/agents/jq_agent.rb · L166 |
| Repository | GitHub · huginn/huginn · Release v2026.11.09 |
| Link | vulncheck.com · advisories/huginn-before-2026.11.09-information-exposure-via-jqagent-jq-env-builtin |
Questions about CVE-2026-127082
Is CVE-2026-127082 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
The JqAgent jq env builtin lets an authenticated user read the Huginn server process environment. Exposed values could include APP_SECRET_TOKEN, database and SMTP credentials, OAuth client secrets, and the invitation code.
Source: github.com
Which versions are affected by CVE-2026-127082?
huginn: before 2026.11.09.
Source: cve.now feed data
Am I affected, and how do I check?
Huginn versions before 2026.11.09 are affected when jq support is enabled through USE_JQ, and the advisory notes versions up to git 86a924f. To check, look at whether USE_JQ is enabled in the installation's configuration and compare the Huginn version against 2026.11.09.
Source: github.com
How do I fix CVE-2026-127082?
Upgrade Huginn to 2026.11.09 or later, which is the listed fixed version.
Source: github.com
Related
- CVE-2026-63769Huginn < 2026.09.09 SSRF via ScenarioImport fetch_url Method
- CVE-2026-127083Huginn from 2026.09.09 before 2026.11.09 SSRF via OUTBOUND_PROXY Bypass
- CVE-2026-123094Huginn before 2026.11.05 Stored XSS via OAuth Service Display Name
- CVE-2026-129030WordPress ShopBuilder – Elementor WooCommerce Builder Addons plugin <= 3.4.3 - Sensitive Data Exposure vulnerability
- CVE-2026-123465WordPress myCred plugin <= 4.0.2 - Sensitive Data Exposure vulnerability
- CVE-2026-119822Windows Overlay Filter Elevation of Privilege Vulnerability
No corrections so far. Something wrong on this page? Report an error.