CVE-2020-15272: In the git-tag-annotation-action (open source GitHub Action) before version 1.0.1, an attacker can execute arb

Q: How do I fix CVE-2020-15272?

git-tag-annotation-action: upgrade to 1.0.1. Exact commands for each OS are on this page.

Q: Is CVE-2020-15272 being exploited?

CVE-2020-15272 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2020-15272 affect?

CVE-2020-15272 affects git-tag-annotation-action. Severity is high (CVSS 8.7). In the git-tag-annotation-action (open source GitHub Action) before version 1.0.1, an attacker can execute arbitrary (*) shell commands if they can control the value of [the `tag` input] or manage to alter the value of [the `GITHUB_REF` env

This month

HIGH 8.7UPGRADE

CVE-2020-15272 is a high-severity flaw (CVSS 8.7) affecting git-tag-annotation-action. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

In the git-tag-annotation-action (open source GitHub Action) before version 1.0.1, an attacker can execute arbitrary (*) shell commands if they can control the value of [the `tag` input] or manage to alter the value of [the `GITHUB_REF` environment variable]. The problem has been patched in version 1.0.1. If you don't use the `tag` input you are most likely safe. The `GITHUB_REF` environment variable is protected by the GitHub Actions environment

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.7 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	Required
EPSS exploit chance	1.2% (top 32%)
CISA exploited list	No
Weakness	CWE-78
Published	2020-10-26
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: git-tag-annotation-action project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2020-10-26 19:15 UTCPublished CVE record published
2026-06-17 02:56 UTCUpdated Record last modified

git-tag-annotation-action project git-tag-annotation-action UPGRADE

Affected: < 1.0.1

Fixed in: 1.0.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy git-tag-annotation-action || rpm -q git-tag-annotation-action || git-tag-annotation-action --version

2. UPGRADE to 1.0.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade git-tag-annotation-action

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade git-tag-annotation-action

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-15272?

git-tag-annotation-action: upgrade to 1.0.1. Exact commands for each OS are on this page.

Is CVE-2020-15272 being exploited?

CVE-2020-15272 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-15272 affect?

CVE-2020-15272 affects git-tag-annotation-action. Severity is high (CVSS 8.7). In the git-tag-annotation-action (open source GitHub Action) before version 1.0.1, an attacker can execute arbitrary (*) shell commands if they can control the value of [the `tag` input] or manage to alter the value of [the `GITHUB_REF` env

How urgent is CVE-2020-15272?

Priority 47/100. High severity

Software pages

GitHub vulnerabilities · Git vulnerabilities

References

← Back to latest CVEs