dbcve.org
GoshsApplication

CVE-2026-40903

CRITICAL · 9.1 CVSS v3.1 Published 2026-04-21
Fix available
A fix is available. Upgrade to 2.0.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
goshs is a SimpleHTTPServer written in Go. Prior to 2.0.0-beta.6, goshs has an ArtiPACKED vulnerability. ArtiPACKED can lead to leakage of the GITHUB_TOKEN through workflow artifacts, even though the token is not present in the repository source code. This vulnerability is fixed in 2.0.0-beta.6.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

goshs prior to 2.0.0-beta.6 contains an ArtiPACKED vulnerability that causes leakage of GITHUB_TOKEN through CI/CD workflow artifacts. Even though the token is not present in the repository source code, the vulnerability allows the token to be exposed in build artifacts, potentially enabling unauthorized access to the GitHub repository.

MitigationUpgrade goshs to version 2.0.0-beta.6 or later to remediate this vulnerability. Additionally, review and rotate any GITHUB_TOKEN that may have been exposed via workflow artifacts, and audit access logs for potential unauthorized repository access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GoshsApplication
Affected:< 2.0.0= 2.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed goshs version
    Run 'goshs --version' or check the binary version metadata
    Affected if Version is below 2.0.0-beta.6 or equals exactly 2.0.0
  2. Check if you build goshs from source
    Review your build pipeline or CI/CD configuration files (such as .github/workflows/) for goshs compilation steps
    Affected if You build goshs yourself and the source version used is vulnerable
  3. Verify GitHub Actions workflow configuration
    Inspect any .github/workflows/*.yml files in your environment for presence of 'GITHUB_TOKEN' or 'secrets.GITHUB_TOKEN' usage in jobs that upload artifacts
    Affected if Workflows upload build artifacts while GITHUB_TOKEN is active and accessible to those artifacts
  4. Inspect artifact storage settings
    Check if your CI/CD artifacts are stored in public repositories or public storage buckets
    Affected if Build artifacts containing potentially leaked tokens are publicly accessible
  5. Audit artifact contents
    Download and examine recent build artifacts for presence of any file resembling a GitHub token (format: gho_*, ghp_*, ghs_*, ghr_*)
    Affected if Tokens matching GitHub token patterns are found in artifact contents

You are affected if you use a goshs version below 2.0.0-beta.6 (or 2.0.0) and have CI/CD workflows that expose build artifacts containing GitHub tokens.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.0.0 or later
Fixed in 2.0.0
Interim mitigation

Upgrade goshs to version 2.0.0-beta.6 or later to remediate this vulnerability. Additionally, review and rotate any GITHUB_TOKEN that may have been exposed via workflow artifacts, and audit access logs for potential unauthorized repository access.

Recommended fix High confidence

goshs version 2.0.0-beta.6 or later

  1. 1. Identify the currently installed goshs version by checking your project dependencies or binary version
  2. 2. Download or install goshs version 2.0.0-beta.6 (or a later stable version if available)
  3. 3. Replace the vulnerable goshs binary or dependency with the fixed version
  4. 4. Verify the installation by checking goshs version output
  5. 5. Review your GitHub Actions workflows to ensure no tokens are being exposed in artifacts
Caveat Review release notes for any changes between your current version and 2.0.0-beta.6

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Goshs Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40903 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-40903 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data