Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-48113

Authorization Flaw in github.com/jpillora/chisel (CVE-2026-48113)

Summary

Vulnerability in github.com/jpillora/chisel (CVE-2026-48113). Risk of unauthorized operations or information disclosure. Exploitable via tunnel.Config. Mitigation: upgrade to 1.11.5 or later.

Original description

The description as published by the source.

Summary

Authenticated chisel clients can bypass --authfile ACL restrictions and tunnel traffic to arbitrary destinations reachable from the server. The ACL is enforced only during the initial handshake against declared remotes, but never on subsequent SSH channels that carry actual traffic. A malicious client authenticates with a permitted remote, then opens channels to any host:port it wants.

Details

The chisel server validates user ACLs in two places but is missing validation in one of the important places.

The server/server_handler.go checks the ACL, during the initial config handshake:

for _, r := range c.Remotes {
    if user != nil {
        addr := r.UserAddr()
        if !user.HasAccess(addr) {
            failed(s.Errorf("access to '%s' denied", addr))
            return
        }
    }
}
r.Reply(true, nil)

This validates the declared remote list from the client's config request. It runs once, at connection setup. But in share/tunnel/tunnel_out_ssh.go ACL aren't being checked, when the server processes actual traffic channels:

func (t *Tunnel) handleSSHChannel(ch ssh.NewChannel) {
    remote := string(ch.ExtraData())        // client-controlled
    hostPort, proto := settings.L4Proto(remote)
    sshChan, reqs, err := ch.Accept()       // accepted unconditionally
    // ...
    err = t.handleTCP(l, stream, hostPort)  // dials whatever client said
}

func (t *Tunnel) handleTCP(l *cio.Logger, src io.ReadWriteCloser, hostPort string)…

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-48113 has been found in github.com/jpillora/chisel.
Attackers can target a specific entry point like tunnel.Config over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/jpillora/chisel to 1.11.5 or later.
If unsure, ask your IT team or search "github.com/jpillora/chisel CVE-2026-48113" on the vendor's site.

CVE-2026-48113 (github.com/jpillora/chisel) — CWE-863
Attack surface: tunnel.Config / server_handler.go / poc.sh / main.go
Patched: 1.11.5 — 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

Incorrect authorization (CWE-863) exists in github.com/jpillora/chisel. Attackers reach the vulnerable code path via tunnel.Config.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/jpillora/chisel. Attack surface: tunnel.Config / server_handler.go / poc.sh / main.go.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.11.5.

🛡️ 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 request patterns matching this CVE's known IOCs. Run grep -r 'github.com/jpillora/chisel' . 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/jpillora/chisel' . | grep -v node_modules

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

  2. 2
    Apply patch patch 
    Upgrade github.com/jpillora/chisel to 1.11.5

    ステージング環境で 1.11.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

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

Affected packages

go github.com/jpillora/chisel
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.11.5"}]}]

References

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