Skip to content
Noroxi
NVD / CVE Program· CNA HashiCorp

CVE-2026-88922: Go-getter vulnerable to a privilege escalation issue in its archive decompression handling

Noroxi assessment

Priority: Monitor (action score 26/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.11% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. A user must open a link or visit a page. Special conditions such as timing or configuration are required.
  • Fixed version: HashiCorp Shared library 1.8.9, 2.2.4.

Low priority for now. Upgrade to HashiCorp Shared library 1.8.9, 2.2.4 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

The go-getter library up to versions 1.8.8 and 2.2.3 is vulnerable to a privilege escalation issue in its archive decompression handling that may allow a crafted archive to cause extracted files to be created with elevated permission bits. Where extraction is performed by a privileged user, this may allow a local actor to obtain the privileges of the extracting process. This vulnerability (CVE-2026-88922) is fixed in go-getter 1.8.9 and 2.2.4.

MediumCVSS 6.7 · v3.1—No exploit Fix available
Published
Sep 15, 2026
Updated
Sep 20, 2026
EPSS
0.1% · 1th percentile

Report tools

JSON

Action score

26

Monitor

Low priority for now.

CVSS
26 / 40 · 6.7 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · HashiCorp
6.7
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-88922

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (HashiCorp). Independent of NVD's CPE analysis and usually ahead of it.

  • HashiCorp Shared library

    • 1.0.1 and later · before 2.2.4affected · semverfixed in 1.8.9

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12golang-github-hashicorp-go-getterfrom 0—
Red Hat:hummingbird:1grypebefore 0:0.118.0-0.2.hum10:0.118.0-0.2.hum1
Red Hat:hummingbird:1opentofu1.10before 0:1.10.10-0.4.hum10:1.10.10-0.4.hum1
Red Hat:hummingbird:1opentofu1.12before 0:1.12.6-0.2.hum10:1.12.6-0.2.hum1
Red Hat:hummingbird:1syftbefore 0:1.51.1-0.2.hum10:1.51.1-0.2.hum1
Red Hat:hummingbird:1trivybefore 0:0.74.0-0.3.hum10:0.74.0-0.3.hum1
SUSE:Linux Enterprise Module for Public Cloud 15 SP4terraform-provider-susepubliccloudbefore 0.0.1-150100.3.26.10.0.1-150100.3.26.1

Other highest-scoring records for the same primary product.

  • CVE-2026-0969Arbitrary code execution in React server-side rendering of untrusted MDX content
    35Monitor
  • CVE-2026-8052Nomad's exec2 task driver vulnerable to arbitrary file read/write on client host through symlink attack
    24Monitor
  • CVE-2026-19585Go-getter vulnerable to a path traversal in S3/GCS directory download handling
    21Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2026-14362Jul 8, 2026 · Denial of service via crafted push/pull gossip message in memberlist
    19Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
HashiCorp Shared library1.8.9Vendor (CNA)
HashiCorp Shared library2.2.4Vendor (CNA)
red hat:grype0:0.118.0-0.2.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:opentofu1.100:1.10.10-0.4.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:opentofu1.120:1.12.6-0.2.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:syft0:1.51.1-0.2.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:trivy0:0.74.0-0.3.hum1 · Red Hat:hummingbird:1Package registry (OSV)
suse:terraform-provider-susepubliccloud0.0.1-150100.3.26.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP4Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • A user must open a link or visit a page.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records