Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go
Not in CISA KEV

GHSA-h563-xh25-x54q

Fix: argoproj/argo-workflows#6285

GHSA-h563-xh25-x54q is a Improper Input Validation vulnerability in github.com/argoproj/argo-workflows/v3. 2 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-h563-xh25-x54q is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Workflow re-write vulnerability using input parameter

Also known asBIT-argo-workflows-2021-37914CVE-2021-37914GO-2022-0928
Published
Aug 9, 2021
Updated
Aug 21, 2024
Affected
1 pkg
Patched
1 / 1
Exploits
2 known
Exploitation data as of Aug 21, 2024 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🐹github.com/argoproj/argo-workflows/v3

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Impact

  • Allow end-users to set input parameters, but otherwise expect workflows to be secure.

Patches

Not yet.

Workarounds

  • Set EXPRESSION_TEMPLATES=false for the workflow controller

References

For more information

If you have any questions or comments about this advisory:

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/argoproj/argo-workflows/v33.1.0&&< 3.1.63.1.6
Exploits & PoCs
2

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/argoproj/argo-workflows/v3. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update github.com/argoproj/argo-workflows/v3 to 3.1.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h563-xh25-x54q is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-h563-xh25-x54q is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-h563-xh25-x54q. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact * Allow end-users to set input parameters, but otherwise expect workflows to be secure. ### Patches Not yet. ### Workarounds * Set `EXPRESSION_TEMPLATES=false` for the workflow controller ### References * https://github.com/argoproj/argo-workflows/issues/6441 ### For more information If you have any questions or comments about this advisory: * Open an issue in [example link to repo](http://example.com) * Email us at [example email address](mailto:[email protected])
O3 Security · Impact-Aware SCA

Is GHSA-h563-xh25-x54q in your dependencies?

O3 detects GHSA-h563-xh25-x54q across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-h563-xh25-x54q: Workflow re-write… | O3 Security