Skip to main content
VulnerabilityPublished

CVE-2026-73564: fatedier frp · Improper Validation of Array Index

Affects fatedier frpSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.7 High : upgrade to 0.70.1 soon.

Data as of 10 Nov 2026, 23:24 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.70.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.

What to do

Upgrade frp and fatedier/frp to 0.70.1.

Affected software

ProductAffectedFixed in
fatedierfrpAffected
  • >=0.53.0 <0.70.1
Fixed in
  • 0.70.1
GitHubfatedier/frppkg:github/fatedier/frpOther threatsAffected
  • <0.70.1 >=0.53.0
Fixed in
  • 0.70.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade frp to version 0.70.1 or later where this issue is fixed. Patch status is confirmed by the vendor stating the fix is in 0.70.1. Until upgrading, ensure an authorized-keys file is configured to prevent unauthenticated access to the vulnerable code path.

Description

frp is a fast reverse proxy. From 0.53.0 until 0.70.1, frp's optional SSH Tunnel Gateway in pkg/ssh/server.go parses an SSH exec channel request by adding 4 to an attacker-controlled four-byte big-endian length. A length of 0xFFFFFFFF makes the uint32 addition wrap to 3, defeats the payload bounds check, and causes payload[4:3] to panic in TunnelServer.handleNewChannel. When no authorized-keys file is configured, sshConfig.NoClientAuth permits an unauthenticated peer to reach this channel phase before the frp token is checked, so a single five-byte request terminates the frps process and drops every active tunnel. This issue is fixed in version 0.70.1.

References

Community reviews

Loading reviews…