Vulnerabilities in pkg:golang/github.com/fatedier/frp
PACKAGECVE-2026-73564 is a HIGH denial of service vulnerability (CWE-190: Integer Overflow or Wraparound) affecting frp libraries in the Go ecosystem. The issue involves unauthenticated remote denial of service in the frp ssh tunnel gateway via integer overflow. Remediation is available by upgrading affected packages to version 0.70.1.
pkg:golang/github.com/fatedier/frp
Vulnerability advisories affecting package pkg:golang/github.com/fatedier/frp. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-26gq-p25f-99cp | CVE-2026-73564 | HIGH | frp: Unauthenticated Remote Denial of Service in the frp SSH Tunnel Gateway via Integer Overflow |
| GHSA-pq96-pwvg-vrr9 | CVE-2026-40910 | MODERATE | frp has an authentication bypass in HTTP vhost routing when routeByHTTPUser is used for access control |
CVE-2026-73564 at a Glance
How to Fix CVE-2026-73564
To remediate this vulnerability, upgrade all affected frp dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade github.com/fatedier/frp to 0.70.1
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for github.com/fatedier/frp
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-73564, inspect your project dependencies for frp:
inspect dependencies for github.com/fatedier/frp
Analyze the terminal output to locate any version of frp in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.70.1), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-190: Integer Overflow or Wraparound, where the product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. this occurs when an integer value is incremented to a value that is too large to store in the associated representation. when this occurs, the value may become a very small or negative number. In frp, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-73564 Affected frp Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
github.com/fatedier/frp
|
Go |
≥ 0.53.0
< 0.70.1
|
0.70.1
|
References
Frequently Asked Questions
What is CVE-2026-73564?
Which frp versions are affected?
What version fixes CVE-2026-73564?
Is github.com/fatedier/frp affected?
What CWE is associated with CVE-2026-73564?
How can I check Go dependencies for CVE-2026-73564?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-26gq-p25f-99cp",
"modified" : "2026-08-13T17:35:53Z",
"published" : "2026-07-24T21:48:04Z",
"aliases" : [ "CVE-2026-73564" ],
"summary" : "frp: Unauthenticated Remote Denial of Service in the frp SSH Tunnel Gateway via Integer Overflow",
"details" : "## Summary\n\nAn integer-overflow vulnerability in the frp server's optional SSH Tunnel Gateway lets any unauthenticated remote attacker crash the entire `frps` process with a single five-byte message. When the gateway parses an SSH `exec` channel request in `pkg/ssh/server.go`, it adds a small constant to a four-byte length value taken directly from the request. Because that length is fully attacker-controlled, a value of `0xFFFFFFFF` makes the addition wrap around to a tiny number, defeating the only bounds check and forcing an out-of-range slice. Go raises a panic that nothing recovers, so the whole server exits. In the default gateway mode SSH clients are not authenticated and the request is handled before any frp token is checked, so the crash is reachable pre-authentication. It carries no state and is trivially repeatable, turning one crash into a sustained outage that drops every tunnel for every user.\n\n## Details\n\nThe `exec` request payload is a four-byte big-endian length followed by that many command bytes, and the length field is fully attacker-controlled. The gateway computes the end of the command as `4 + length`. The constant `4` takes the `uint32` type of the length field, so `4 + 0xFFFFFFFF` wraps modulo 2^32 to `3`. The only guard compares the real payload size against this wrapped value, so a five-byte payload passes the test `5 < 3`, and the slice runs from index 4 to index 3:\n\n```go\n// pkg/ssh/server.go:315-319\nend := 4 + binary.BigEndian.Uint32(req.Payload[:4]) // 4 + 0xFFFFFFFF wraps to 3\nif len(req.Payload) < int(end) { // 5 < 3 is false, so it passes\n continue\n}\nextraPayload := string(req.Payload[4:end]) // payload[4:3] -> panic\n```\n\nThe handler runs in a bare goroutine and no function in the call chain installs a `recover`, so the panic unwinds to the top of the goroutine and terminates the whole process rather than the single connection:\n\n```go\n// pkg/ssh/server.go:226\ngo s.handleNewChannel(newChannel, extraPayloadCh) // no recover anywhere in the chain\n```\n\nThe sink is reachable without credentials in the default configuration. When no authorized-keys file is set, the gateway disables SSH client authentication, which is the default and documented mode where users authenticate through the frp token embedded in the SSH command. The `exec` request is processed during the channel phase, before that token is validated, so an unauthenticated peer reaches the sink:\n\n```go\n// pkg/ssh/gateway.go:74\nsshConfig.NoClientAuth = cfg.AuthorizedKeysFile == \"\" // default: no client auth\n```\n\nAffected product: frp (fatedier), `frps` server, SSH Tunnel Gateway\nAffected versions: v0.53.0 (when the gateway was introduced) through v0.70.0, confirmed against a v0.70.0 build\n\n## PoC\n\nThe SSH Tunnel Gateway must be enabled with no authorized-keys file, which is the default mode of any deployment that turns the gateway on. No credentials and no knowledge of the target are required.\n\nEnable the gateway on a stock v0.70.0 build:\n\n```toml\nbindPort = 7000\n\n[sshTunnelGateway]\nbindPort = 2200\n```\n\nAs an unauthenticated SSH client, open a session channel and send one `exec` request whose four-byte length prefix is `0xFFFFFFFF` followed by a single byte, giving the five-byte payload `ff ff ff ff 41`. The server immediately panics and exits:\n\n```text\npanic: runtime error: slice bounds out of range [4:3]\n...github.com/fatedier/frp/pkg/ssh.(*TunnelServer).handleNewChannel\n .../frp/pkg/ssh/server.go:319\n```\n\nThe shell prompt returns in the server terminal, confirming the whole process has terminated and every other client tunnel is dropped at the same instant. A well-formed request of the same length (prefix `1`) leaves the server running, proving the crash is caused by the overflow value and not by the `exec` request itself. The attacker can re-send the payload after any restart to hold the server down indefinitely.\n\n## Impact\n\nThis is an unauthenticated remote denial of service (CWE-190) leading to an out-of-range array index (CWE-129) and an unhandled process crash (CWE-755). A single five-byte, credential-free message kills the entire `frps` process. Because one `frps` commonly multiplexes the tunnels of many clients, the crash drops every active tunnel for every tenant at once and new logins are refused until the process is restarted, and re-sending the payload after each restart keeps the service down indefinitely (CWE-400). There is no confidentiality or integrity impact and no code execution.\n\nThis issue only affects frps instances with the SSH tunnel gateway explicitly enabled. The SSH tunnel gateway is disabled by default and is not commonly used in typical frps deployments. Default frps configurations are not affected.",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/fatedier/frp"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0.53.0"
}, {
"fixed" : "0.70.1"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 0.70.0"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/fatedier/frp/security/advisories/GHSA-26gq-p25f-99cp"
}, {
"type" : "WEB",
"url" : "https://github.com/fatedier/frp/pull/5428"
}, {
"type" : "WEB",
"url" : "https://github.com/fatedier/frp/commit/7dc7be930e2452ae93fd32f2a77f8c6fcd0b652b"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/fatedier/frp"
}, {
"type" : "WEB",
"url" : "https://github.com/fatedier/frp/releases/tag/v0.70.1"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-129", "CWE-190" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-07-24T21:48:04Z",
"nvd_published_at" : null
}
}