Missing Authentication for Critical Function Affecting rubygem-smart_proxy_dynflow package, versions *


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.38% (30th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL7-RUBYGEMSMARTPROXYDYNFLOW-21089290
  • published16 Oct 2026
  • disclosed7 Oct 2026

Introduced: 7 Oct 2026

NewCVE-2026-107151  (opens in a new tab)
CWE-306  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:7 rubygem-smart_proxy_dynflow.

NVD Description

Note: Versions mentioned in the description apply only to the upstream rubygem-smart_proxy_dynflow package and not the rubygem-smart_proxy_dynflow package as distributed by RHEL. See How to fix? for RHEL:7 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1