VulertSecurity VulertSecurity

Vulnerability Database · GitHub Actions · Package report

step-security/harden-runner: vulnerability history, versions and safety

step-security/harden-runner is a package in the GitHub Actions ecosystem. Vulert records 5 vulnerabilities for it across 4 affected ranges, from Nov 2024 to Mar 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded M4 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 in the last 12 months

Most recent disclosure 17 Mar 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all step-security/harden-runner vulnerabilities

Vulert verdict on step-security/harden-runner i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 17 Mar 2026. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 5 vulnerabilities on record across 1 year, 3 in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 5 over 1 year · 3 in the last year i
  • Latest disclosure 17 Mar 2026 i
  • Highest CVSS 8.8 i
  • With no published fix 0 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

i
Affected range Vulnerabilities
up to 2.16.0 (exclusive) 2
up to 2.14.2 (exclusive) 1
from 0.12.0 up to 2.12.0 (exclusive) 1
up to 2.10.2 (exclusive) 1

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1
  • 2025 1
  • 2026 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 3 of the 5 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for step-security/harden-runner

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-52587: Command Injection Vulnerability in step-security/harden-runner 8.8 low 2.10.2 18 Nov 2024
CVE-2025-32955: Harden-Runner Privilege Escalation via Docker Evasion 6.0 medium 2.12.0 22 Apr 2025
CVE-2026-25598: Harden-Runner Package Allows Bypassing of Outbound Connection Logging 6.0 medium 2.14.2 09 Feb 2026
CVE-2026-32947: Egress Policy Bypass in Harden-Runner (Community Tier) via DNS over HTTPS 4.6 medium 2.16.0 17 Mar 2026
CVE-2026-32946: step-security/harden-runner Egress Policy Bypass via DNS over TCP 4.6 medium 2.16.0 17 Mar 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About step-security/harden-runner

Is step-security/harden-runner safe to use?

Vulert records 5 vulnerabilities for step-security/harden-runner in GitHub Actions: 0 critical, 0 high, 4 medium and 1 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does step-security/harden-runner have?

5 vulnerabilities are recorded for step-security/harden-runner in the GitHub Actions ecosystem: 0 critical, 0 high, 4 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new step-security/harden-runner vulnerabilities disclosed?

3 vulnerabilities were recorded for step-security/harden-runner in the last 12 months, and the oldest entry in this database dates to 18 Nov 2024. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of step-security/harden-runner are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor step-security/harden-runner for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the step-security/harden-runner version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.