# CVE-2026-107151: Rubygem-smart_proxy_dynflow: task update and done callbacks accept unauthenticated requests

> Attackers can manipulate job results in Red Hat Satellite when remote execution uses pull modes, requiring knowledge of job identifiers.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Oct 2026
- **Updated:** 10 Oct 2026
- **Also known as:** GHSA-gfwx-437h-g22q

## What is CVE-2026-107151?

CVE-2026-107151 is a medium-severity missing authorization vulnerability in Red Hat Satellite 6, published on 7 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Missing authentication has been found in remote-execution task updates in the smart_proxy_dynflow package. The progress and completion callbacks accept a report when the one-time token is missing. A network attacker or user must already know the identifier of a running job. This applies when remote execution is set to pull or pull-mqtt mode. They can send their own job output and mark the job as a success or a failure. The job is then recorded with that result.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-107151 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-107151 is a medium-severity missing authorization vulnerability in Red Hat Satellite 6, published on 7 Oct 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 CVE-2026-107151 in the wild and no public exploit code.

Affected product: Red Hat Satellite 6. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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