# CVE-2026-127082: Huginn before 2026.11.09 Information Exposure via JqAgent jq env Builtin


- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Nov 2026
- **Updated:** 13 Nov 2026
- **Also known as:** GHSA-3f56-748g-q34j, GHSA-w8pv-mr4h-2g9v

## What is CVE-2026-127082?

CVE-2026-127082 is a high-severity vulnerability in huginn, published on 13 Nov 2026. 

### Official 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.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere)

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

1 open source package ship an affected version, including huginn/huginn.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `huginn/huginn` | GitHub | `pkg:github/huginn/huginn` | All versions | 2026.11.09 |

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

Upgrade huginn/huginn to 2026.11.09 or later.

## Is CVE-2026-127082 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-127082 is a high-severity vulnerability in huginn, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-127082 in the wild and no public exploit code.

Affected packages and fixed versions:
- huginn/huginn (GitHub): affected all versions; fixed in 2026.11.09

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

## Sources

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

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