Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-54719 high CVSS 7.5

Vulnerability in github.com/patrickhener/goshs (CVE-2026-54719)

Summary

Vulnerability in github.com/patrickhener/goshs (CVE-2026-54719). Confidential information can be exposed externally. Exploitable via GET /protected/secret.txt. Mitigation: upgrade to 2.1.1 or later.

Original description

The description as published by the source.

GHSA-wvhv-qcqf-f3cx fixed the per-folder .goshs ACL bypass on the state-changing routes (PUT/POST upload/?mkdir/?delete) and added recursive ACL resolution, and its description states the read/list path correctly enforces .goshs. That premise does not hold for the ?bulk zip-download route. bulkDownload (httpserver/updown.go) takes one or more ?file= parameters, runs each through sanitizePath(fs.Webroot, file), and streams the contents back as a ZIP without ever calling findEffectiveACL/applyCustomAuth. It is dispatched from earlyBreakParameters (?bulk) before the normal doDir/doFile/sendFile flow that performs the ACL check. An unauthenticated attacker can therefore read any file under the webroot protected solely by a .goshs ACL, bypassing both the folder auth (401 on the normal path) and the per-file block list (404 on the normal path). Same authorization-inconsistency root cause as the original advisory, surviving on a read route the fix did not cover.

Proof of concept (live, against the fixed v2.1.0 build which includes fix commit f212c4f4, served with no global -b auth, only a per-folder .goshs):
GET /protected/secret.txt -> 401 (ACL enforced on normal path)
GET /protected/secret.txt -u admin:admin -> 200
GET /?bulk&file=/protected/secret.txt -> 200, zip contains the protected file contents (BYPASS)
GET /?bulk&file=/protected/blocked.txt -> 200, zip contains the block-listed file (block bypass)
GET /protected/secret.txt?share -> 40…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-54719 has been found in github.com/patrickhener/goshs.
Attackers can target a specific entry point like GET /protected/secret.txt over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade github.com/patrickhener/goshs to 2.1.1 or later.
If unsure, ask your IT team or search "github.com/patrickhener/goshs CVE-2026-54719" on the vendor's site.

CVE-2026-54719 (github.com/patrickhener/goshs) — CWE-862 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GET /protected/secret.txt
Patched: 2.1.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-862) exists in github.com/patrickhener/goshs. Attackers reach the vulnerable code path via GET /protected/secret.txt without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/patrickhener/goshs. Attack surface: GET /protected/secret.txt.

🔥 Severity

Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 2.1.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual GET /protected/secret.txt requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/patrickhener/goshs' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/patrickhener/goshs' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/patrickhener/goshs を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'GET /protected/secret.txt' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで GET /protected/secret.txt への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch 
    Upgrade github.com/patrickhener/goshs to 2.1.1

    ステージング環境で 2.1.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify 
    Replay attack against GET /protected/secret.txt on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

go github.com/patrickhener/goshs
[{"type":"SEMVER","events":[{"introduced":"0"},{"last_affected":"1.1.4"}]}]
go github.com/patrickhener/goshs/v2
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.1.1"}]}]
go goshs.de/goshs
[{"type":"SEMVER","events":[{"introduced":"0"},{"last_affected":"1.1.4"}]}]
go goshs.de/goshs/v2
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.1.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details