Update module github.com/labstack/echo/v4 to v4.15.3 [SECURITY]

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
github.com/labstack/echo/v4	v4.13.3 → v4.15.3

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Echo: Encoded slash (%2F) bypasses route-level protection and exposes static files

CVE-2026-55677 / GHSA-vfp3-v2gw-7wfq

More information

Details

Summary

Echo's router and static file handler disagree on URL path decoding. The router matches routes using the raw encoded path (preserving %2F as-is), while StaticDirectoryHandler unescapes %2F to / before resolving filesystem paths. This allows an attacker to bypass route-level access controls and read static files without authorization.

Details

Root cause 1 — router.go lines 798-802:
The router uses req.URL.RawPath for route matching when useEscapedPathForRouting is false (the default). This means /admin%2Fsecret.txt is treated as a single path segment and does NOT match the /admin/* route pattern.

if!r.useEscapedPathForRouting&&req.URL.RawPath!="" {
path=req.URL.RawPath
}

Root cause 2 — echo.go lines 559-568:
StaticDirectoryHandler calls url.PathUnescape() on the path parameter before opening files. This converts %2F back to /, resolving admin/secret.txt on disk.

if!disablePathUnescaping {
tmpPath, err:=url.PathUnescape(p)
p=tmpPath
}
name:=filepath.ToSlash(filepath.Clean(strings.TrimPrefix(p, "/")))

PoC (Screenshot)

Sample:

403:

Bypass with encoded slash:

Impact

Unauthorized static file disclosure. Applications that protect route prefixes with authentication middleware while also serving static files from a broader root are vulnerable. An attacker only needs to encode the slash (/ → %2F) in the URL to bypass all route-level protection.

Common affected pattern:

adminGroup:=e.Group("/admin", authMiddleware)
e.StaticFS("/", os.DirFS("public"))

Severity

• CVSS Score: 7.5 / 10 (High)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

References

• https://github.com/labstack/echo/security/advisories/GHSA-vfp3-v2gw-7wfq
• https://nvd.nist.gov/vuln/detail/CVE-2026-55677
• https://github.com/labstack/echo/pull/3009
• https://github.com/labstack/echo/pull/3011
• https://github.com/labstack/echo/commit/8d1ae9d3360a71672418856d58753af25f2c3986
• https://github.com/labstack/echo/commit/c3fa2a27ff92b2b8db360de614f999ef1da24725
• https://github.com/labstack/echo/releases/tag/v4.15.3
• https://github.com/labstack/echo/releases/tag/v5.2.0
• https://github.com/advisories/GHSA-vfp3-v2gw-7wfq

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

labstack/echo (github.com/labstack/echo/v4)

v4.15.3: - Static encoded-separator route bypass fix (GHSA-vfp3-v2gw-7wfq)

Compare Source

Security

• fix(static): reject encoded path separators that bypass route-level middleware by @​vishr in #​3011

Fixes GHSA-vfp3-v2gw-7wfq: an encoded path separator (%2F or %5C) in a static file URL could bypass route-level middleware (e.g. authentication on a sibling route) and disclose static files. Both StaticDirectoryHandler (used by Static/StaticFS) and the Static middleware are affected. Backport of the v5 fix (#​3009, released in v5.2.0). Thanks to @​a-tt-om and @​oran-gugu for reporting.

Full Changelog: labstack/echo@v4.15.2...v4.15.3

v4.15.2: - Context.Scheme() header validation

Compare Source

Security

• Context.Scheme() should validate values taken from header by @​aldas in #​2962

Thanks to @​shblue21 for reporting this issue.

Full Changelog: labstack/echo@v4.15.1...v4.15.2

v4.15.1

Compare Source

What's Changed

• CSRF: support older token-based CSRF protection handler that want to render token into template by @​aldas in #​2905

Full Changelog: labstack/echo@v4.15.0...v4.15.1

v4.15.0

Compare Source

Security

NB: If your application relies on cross-origin or same-site (same subdomain) requests do not blindly push this version to production

The CSRF middleware now supports the Sec-Fetch-Site header as a modern, defense-in-depth approach to CSRF
protection, implementing the OWASP-recommended Fetch Metadata API alongside the traditional token-based mechanism.

How it works:

Modern browsers automatically send the Sec-Fetch-Site header with all requests, indicating the relationship
between the request origin and the target. The middleware uses this to make security decisions:

• same-origin or none: Requests are allowed (exact origin match or direct user navigation)
• same-site: Falls back to token validation (e.g., subdomain to main domain)
• cross-site: Blocked by default with 403 error for unsafe methods (POST, PUT, DELETE, PATCH)

For browsers that don't send this header (older browsers), the middleware seamlessly falls back to
traditional token-based CSRF protection.

New Configuration Options:

• TrustedOrigins []string: Allowlist specific origins for cross-site requests (useful for OAuth callbacks, webhooks)
• AllowSecFetchSiteFunc func(echo.Context) (bool, error): Custom logic for same-site/cross-site request validation

Example:

e.Use(middleware.CSRFWithConfig(middleware.CSRFConfig{
// Allow OAuth callbacks from trusted providerTrustedOrigins: []string{"https://oauth-provider.com"},
// Custom validation for same-site requestsAllowSecFetchSiteFunc: func(c echo.Context) (bool, error) {
// Your custom authorization logic herereturnvalidateCustomAuth(c), nil// return true, err // blocks request with error// return true, nil // allows CSRF request through// return false, nil // falls back to legacy token logic
},
}))

PR: #​2858

Type-Safe Generic Parameter Binding

• Added generic functions for type-safe parameter extraction and context access by @​aldas in #​2856

  Echo now provides generic functions for extracting path, query, and form parameters with automatic type conversion,
  eliminating manual string parsing and type assertions.

  New Functions:

  • Path parameters: PathParam[T], PathParamOr[T]
  • Query parameters: QueryParam[T], QueryParamOr[T], QueryParams[T], QueryParamsOr[T]
  • Form values: FormParam[T], FormParamOr[T], FormParams[T], FormParamsOr[T]
  • Context store: ContextGet[T], ContextGetOr[T]

  Supported Types:
  Primitives (bool, string, int/uint variants, float32/float64), time.Duration, time.Time
  (with custom layouts and Unix timestamp support), and custom types implementing BindUnmarshaler,
  TextUnmarshaler, or JSONUnmarshaler.

  Example:

  // Before: Manual parsingidStr:=c.Param("id")
  id, err:=strconv.Atoi(idStr)
  // After: Type-safe with automatic parsingid, err:=echo.PathParam[int](c, "id")
  // With default valuespage, err:=echo.QueryParamOr[int](c, "page", 1)
  limit, err:=echo.QueryParamOr[int](c, "limit", 20)
  // Type-safe context access (no more panics from type assertions)user, err:=echo.ContextGet[*User](c, "user")

PR: #​2856

DEPRECATION NOTICE Timeout Middleware Deprecated - Use ContextTimeout Instead

The middleware.Timeout middleware has been deprecated due to fundamental architectural issues that cause
data races. Use middleware.ContextTimeout or middleware.ContextTimeoutWithConfig instead.

Why is this being deprecated?

The Timeout middleware manipulates response writers across goroutine boundaries, which causes data races that
cannot be reliably fixed without a complete architectural redesign. The middleware:

• Swaps the response writer using http.TimeoutHandler
• Must be the first middleware in the chain (fragile constraint)
• Can cause races with other middleware (Logger, metrics, custom middleware)
• Has been the source of multiple race condition fixes over the years

What should you use instead?

The ContextTimeout middleware (available since v4.12.0) provides timeout functionality using Go's standard
context mechanism. It is:

• Race-free by design
• Can be placed anywhere in the middleware chain
• Simpler and more maintainable
• Compatible with all other middleware

Migration Guide:

// Before (deprecated):e.Use(middleware.Timeout())
// After (recommended):e.Use(middleware.ContextTimeout(30*time.Second))

Important Behavioral Differences:

1. Handler cooperation required: With ContextTimeout, your handlers must check context.Done() for cooperative
   cancellation. The old Timeout middleware would send a 503 response regardless of handler cooperation, but had
   data race issues.

2. Error handling: ContextTimeout returns errors through the standard error handling flow. Handlers that receive
   context.DeadlineExceeded should handle it appropriately:

e.GET("/long-task", func(c echo.Context) error {
ctx:=c.Request().Context()
// Example: database query with contextresult, err:=db.QueryContext(ctx, "SELECT * FROM large_table")
iferr!=nil {
iferrors.Is(err, context.DeadlineExceeded) {
// Handle timeoutreturnecho.NewHTTPError(http.StatusServiceUnavailable, "Request timeout")
}
returnerr
}
returnc.JSON(http.StatusOK, result)
})

3. Background tasks: For long-running background tasks, use goroutines with context:

e.GET("/async-task", func(c echo.Context) error {
ctx:=c.Request().Context()
resultCh:=make(chanResult, 1)
errCh:=make(chanerror, 1)
gofunc() {
result, err:=performLongTask(ctx)
iferr!=nil {
errCh<-errreturn
}
resultCh<-result
}()
select {
caseresult:=<-resultCh:
returnc.JSON(http.StatusOK, result)
caseerr:=<-errCh:
returnerrcase<-ctx.Done():
returnecho.NewHTTPError(http.StatusServiceUnavailable, "Request timeout")
}
})

Enhancements

• Fixes by @​aldas in #​2852
• Generic functions by @​aldas in #​2856
• CRSF with Sec-Fetch-Site checks by @​aldas in #​2858

v4.14.0

Compare Source

middleware.Logger has been deprecated. For request logging, use middleware.RequestLogger or
middleware.RequestLoggerWithConfig.

middleware.RequestLogger replaces middleware.Logger, offering comparable configuration while relying on the
Go standard library’s new slog logger.

The previous default output format was JSON. The new default follows the standard slog logger settings.
To continue emitting request logs in JSON, configure slog accordingly:

slog.SetDefault(slog.New(slog.NewJSONHandler(os.Stdout, nil)))
e.Use(middleware.RequestLogger())

Security

• Logger middleware json string escaping and deprecation by @​aldas in #​2849

Enhancements

• Update deps by @​aldas in #​2807
• refactor to use reflect.TypeFor by @​cuiweixie in #​2812
• Use Go 1.25 in CI by @​aldas in #​2810
• Modernize context.go by replacing interface{} with any by @​vishr in #​2822
• Fix typo in SetParamValues comment by @​vishr in #​2828
• Fix typo in ContextTimeout middleware comment by @​vishr in #​2827
• Improve BasicAuth middleware: use strings.Cut and RFC compliance by @​vishr in #​2825
• Fix duplicate plus operator in router backtracking logic by @​yuya-morimoto in #​2832
• Replace custom private IP range check with built-in net.IP.IsPrivate by @​kumapower17 in #​2835
• Ensure proxy connection is closed in proxyRaw function(#​2837) by @​kumapower17 in #​2838
• Update deps by @​aldas in #​2843
• Update golang.org/x/* deps by @​aldas in #​2850

v4.13.4

Compare Source

Enhancements

• chore: fix some typos in comment by @​zhuhaicity in #​2735
• CI: test with Go 1.24 by @​aldas in #​2748
• Add support for TLS WebSocket proxy by @​t-ibayashi-safie in #​2762

Security

• Update dependencies for GO-2025-3487, GO-2025-3503 and GO-2025-3595 in #​2780

---

Configuration

📅 Schedule: (in timezone Asia/Tokyo)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

ℹ️ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 12 additional dependencies were updated
• The go directive was updated for compatibility reasons

Details:

Package	Change
go	1.24.2 -> 1.25.0
github.com/stretchr/testify	v1.10.0 -> v1.11.1
github.com/labstack/gommon	v0.4.2 -> v0.5.0
github.com/mattn/go-colorable	v0.1.13 -> v0.1.14
github.com/mattn/go-isatty	v0.0.20 -> v0.0.22
golang.org/x/crypto	v0.36.0 -> v0.50.0
golang.org/x/mod	v0.24.0 -> v0.34.0
golang.org/x/net	v0.37.0 -> v0.53.0
golang.org/x/sync	v0.13.0 -> v0.20.0
golang.org/x/sys	v0.31.0 -> v0.43.0
golang.org/x/text	v0.23.0 -> v0.36.0
golang.org/x/time	v0.8.0 -> v0.15.0
golang.org/x/tools	v0.31.0 -> v0.43.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
github.com/labstack/echo/v4	v4.13.3 → v4.15.3

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Echo: Encoded slash (%2F) bypasses route-level protection and exposes static files

CVE-2026-55677 / GHSA-vfp3-v2gw-7wfq

More information

Details

Summary

Echo's router and static file handler disagree on URL path decoding. The router matches routes using the raw encoded path (preserving %2F as-is), while StaticDirectoryHandler unescapes %2F to / before resolving filesystem paths. This allows an attacker to bypass route-level access controls and read static files without authorization.

Details

Root cause 1 — router.go lines 798-802:
The router uses req.URL.RawPath for route matching when useEscapedPathForRouting is false (the default). This means /admin%2Fsecret.txt is treated as a single path segment and does NOT match the /admin/* route pattern.

if!r.useEscapedPathForRouting&&req.URL.RawPath!="" {
path=req.URL.RawPath
}

Root cause 2 — echo.go lines 559-568:
StaticDirectoryHandler calls url.PathUnescape() on the path parameter before opening files. This converts %2F back to /, resolving admin/secret.txt on disk.

if!disablePathUnescaping {
tmpPath, err:=url.PathUnescape(p)
p=tmpPath
}
name:=filepath.ToSlash(filepath.Clean(strings.TrimPrefix(p, "/")))

PoC (Screenshot)

Sample:

403:

Bypass with encoded slash:

Impact

Unauthorized static file disclosure. Applications that protect route prefixes with authentication middleware while also serving static files from a broader root are vulnerable. An attacker only needs to encode the slash (/ → %2F) in the URL to bypass all route-level protection.

Common affected pattern:

adminGroup:=e.Group("/admin", authMiddleware)
e.StaticFS("/", os.DirFS("public"))

Severity

• CVSS Score: 7.5 / 10 (High)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

References

• https://github.com/labstack/echo/security/advisories/GHSA-vfp3-v2gw-7wfq
• https://nvd.nist.gov/vuln/detail/CVE-2026-55677
• https://github.com/labstack/echo/pull/3009
• https://github.com/labstack/echo/pull/3011
• https://github.com/labstack/echo/commit/8d1ae9d3360a71672418856d58753af25f2c3986
• https://github.com/labstack/echo/commit/c3fa2a27ff92b2b8db360de614f999ef1da24725
• https://github.com/labstack/echo/releases/tag/v4.15.3
• https://github.com/labstack/echo/releases/tag/v5.2.0
• https://github.com/advisories/GHSA-vfp3-v2gw-7wfq

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

labstack/echo (github.com/labstack/echo/v4)

v4.15.3: - Static encoded-separator route bypass fix (GHSA-vfp3-v2gw-7wfq)

Compare Source

Security

• fix(static): reject encoded path separators that bypass route-level middleware by @​vishr in #​3011

Fixes GHSA-vfp3-v2gw-7wfq: an encoded path separator (%2F or %5C) in a static file URL could bypass route-level middleware (e.g. authentication on a sibling route) and disclose static files. Both StaticDirectoryHandler (used by Static/StaticFS) and the Static middleware are affected. Backport of the v5 fix (#​3009, released in v5.2.0). Thanks to @​a-tt-om and @​oran-gugu for reporting.

Full Changelog: labstack/echo@v4.15.2...v4.15.3

v4.15.2: - Context.Scheme() header validation

Compare Source

Security

• Context.Scheme() should validate values taken from header by @​aldas in #​2962

Thanks to @​shblue21 for reporting this issue.

Full Changelog: labstack/echo@v4.15.1...v4.15.2

v4.15.1

Compare Source

What's Changed

• CSRF: support older token-based CSRF protection handler that want to render token into template by @​aldas in #​2905

Full Changelog: labstack/echo@v4.15.0...v4.15.1

v4.15.0

Compare Source

Security

NB: If your application relies on cross-origin or same-site (same subdomain) requests do not blindly push this version to production

The CSRF middleware now supports the Sec-Fetch-Site header as a modern, defense-in-depth approach to CSRF
protection, implementing the OWASP-recommended Fetch Metadata API alongside the traditional token-based mechanism.

How it works:

Modern browsers automatically send the Sec-Fetch-Site header with all requests, indicating the relationship
between the request origin and the target. The middleware uses this to make security decisions:

• same-origin or none: Requests are allowed (exact origin match or direct user navigation)
• same-site: Falls back to token validation (e.g., subdomain to main domain)
• cross-site: Blocked by default with 403 error for unsafe methods (POST, PUT, DELETE, PATCH)

For browsers that don't send this header (older browsers), the middleware seamlessly falls back to
traditional token-based CSRF protection.

New Configuration Options:

• TrustedOrigins []string: Allowlist specific origins for cross-site requests (useful for OAuth callbacks, webhooks)
• AllowSecFetchSiteFunc func(echo.Context) (bool, error): Custom logic for same-site/cross-site request validation

Example:

e.Use(middleware.CSRFWithConfig(middleware.CSRFConfig{
// Allow OAuth callbacks from trusted providerTrustedOrigins: []string{"https://oauth-provider.com"},
// Custom validation for same-site requestsAllowSecFetchSiteFunc: func(c echo.Context) (bool, error) {
// Your custom authorization logic herereturnvalidateCustomAuth(c), nil// return true, err // blocks request with error// return true, nil // allows CSRF request through// return false, nil // falls back to legacy token logic
},
}))

PR: #​2858

Type-Safe Generic Parameter Binding

• Added generic functions for type-safe parameter extraction and context access by @​aldas in #​2856

  Echo now provides generic functions for extracting path, query, and form parameters with automatic type conversion,
  eliminating manual string parsing and type assertions.

  New Functions:

  • Path parameters: PathParam[T], PathParamOr[T]
  • Query parameters: QueryParam[T], QueryParamOr[T], QueryParams[T], QueryParamsOr[T]
  • Form values: FormParam[T], FormParamOr[T], FormParams[T], FormParamsOr[T]
  • Context store: ContextGet[T], ContextGetOr[T]

  Supported Types:
  Primitives (bool, string, int/uint variants, float32/float64), time.Duration, time.Time
  (with custom layouts and Unix timestamp support), and custom types implementing BindUnmarshaler,
  TextUnmarshaler, or JSONUnmarshaler.

  Example:

  // Before: Manual parsingidStr:=c.Param("id")
  id, err:=strconv.Atoi(idStr)
  // After: Type-safe with automatic parsingid, err:=echo.PathParam[int](c, "id")
  // With default valuespage, err:=echo.QueryParamOr[int](c, "page", 1)
  limit, err:=echo.QueryParamOr[int](c, "limit", 20)
  // Type-safe context access (no more panics from type assertions)user, err:=echo.ContextGet[*User](c, "user")

PR: #​2856

DEPRECATION NOTICE Timeout Middleware Deprecated - Use ContextTimeout Instead

The middleware.Timeout middleware has been deprecated due to fundamental architectural issues that cause
data races. Use middleware.ContextTimeout or middleware.ContextTimeoutWithConfig instead.

Why is this being deprecated?

The Timeout middleware manipulates response writers across goroutine boundaries, which causes data races that
cannot be reliably fixed without a complete architectural redesign. The middleware:

• Swaps the response writer using http.TimeoutHandler
• Must be the first middleware in the chain (fragile constraint)
• Can cause races with other middleware (Logger, metrics, custom middleware)
• Has been the source of multiple race condition fixes over the years

What should you use instead?

The ContextTimeout middleware (available since v4.12.0) provides timeout functionality using Go's standard
context mechanism. It is:

• Race-free by design
• Can be placed anywhere in the middleware chain
• Simpler and more maintainable
• Compatible with all other middleware

Migration Guide:

// Before (deprecated):e.Use(middleware.Timeout())
// After (recommended):e.Use(middleware.ContextTimeout(30*time.Second))

Important Behavioral Differences:

1. Handler cooperation required: With ContextTimeout, your handlers must check context.Done() for cooperative
   cancellation. The old Timeout middleware would send a 503 response regardless of handler cooperation, but had
   data race issues.

2. Error handling: ContextTimeout returns errors through the standard error handling flow. Handlers that receive
   context.DeadlineExceeded should handle it appropriately:

e.GET("/long-task", func(c echo.Context) error {
ctx:=c.Request().Context()
// Example: database query with contextresult, err:=db.QueryContext(ctx, "SELECT * FROM large_table")
iferr!=nil {
iferrors.Is(err, context.DeadlineExceeded) {
// Handle timeoutreturnecho.NewHTTPError(http.StatusServiceUnavailable, "Request timeout")
}
returnerr
}
returnc.JSON(http.StatusOK, result)
})

3. Background tasks: For long-running background tasks, use goroutines with context:

e.GET("/async-task", func(c echo.Context) error {
ctx:=c.Request().Context()
resultCh:=make(chanResult, 1)
errCh:=make(chanerror, 1)
gofunc() {
result, err:=performLongTask(ctx)
iferr!=nil {
errCh<-errreturn
}
resultCh<-result
}()
select {
caseresult:=<-resultCh:
returnc.JSON(http.StatusOK, result)
caseerr:=<-errCh:
returnerrcase<-ctx.Done():
returnecho.NewHTTPError(http.StatusServiceUnavailable, "Request timeout")
}
})

Enhancements

• Fixes by @​aldas in #​2852
• Generic functions by @​aldas in #​2856
• CRSF with Sec-Fetch-Site checks by @​aldas in #​2858

v4.14.0

Compare Source

middleware.Logger has been deprecated. For request logging, use middleware.RequestLogger or
middleware.RequestLoggerWithConfig.

middleware.RequestLogger replaces middleware.Logger, offering comparable configuration while relying on the
Go standard library’s new slog logger.

The previous default output format was JSON. The new default follows the standard slog logger settings.
To continue emitting request logs in JSON, configure slog accordingly:

slog.SetDefault(slog.New(slog.NewJSONHandler(os.Stdout, nil)))
e.Use(middleware.RequestLogger())

Security

• Logger middleware json string escaping and deprecation by @​aldas in #​2849

Enhancements

• Update deps by @​aldas in #​2807
• refactor to use reflect.TypeFor by @​cuiweixie in #​2812
• Use Go 1.25 in CI by @​aldas in #​2810
• Modernize context.go by replacing interface{} with any by @​vishr in #​2822
• Fix typo in SetParamValues comment by @​vishr in #​2828
• Fix typo in ContextTimeout middleware comment by @​vishr in #​2827
• Improve BasicAuth middleware: use strings.Cut and RFC compliance by @​vishr in #​2825
• Fix duplicate plus operator in router backtracking logic by @​yuya-morimoto in #​2832
• Replace custom private IP range check with built-in net.IP.IsPrivate by @​kumapower17 in #​2835
• Ensure proxy connection is closed in proxyRaw function(#​2837) by @​kumapower17 in #​2838
• Update deps by @​aldas in #​2843
• Update golang.org/x/* deps by @​aldas in #​2850

v4.13.4

Compare Source

Enhancements

• chore: fix some typos in comment by @​zhuhaicity in #​2735
• CI: test with Go 1.24 by @​aldas in #​2748
• Add support for TLS WebSocket proxy by @​t-ibayashi-safie in #​2762

Security

• Update dependencies for GO-2025-3487, GO-2025-3503 and GO-2025-3595 in #​2780

---

Configuration

📅 Schedule: (in timezone Asia/Tokyo)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

ℹ️ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 12 additional dependencies were updated
• The go directive was updated for compatibility reasons

Details:

Package	Change
go	1.24.2 -> 1.25.0
github.com/stretchr/testify	v1.10.0 -> v1.11.1
github.com/labstack/gommon	v0.4.2 -> v0.5.0
github.com/mattn/go-colorable	v0.1.13 -> v0.1.14
github.com/mattn/go-isatty	v0.0.20 -> v0.0.22
golang.org/x/crypto	v0.36.0 -> v0.50.0
golang.org/x/mod	v0.24.0 -> v0.34.0
golang.org/x/net	v0.37.0 -> v0.53.0
golang.org/x/sync	v0.13.0 -> v0.20.0
golang.org/x/sys	v0.31.0 -> v0.43.0
golang.org/x/text	v0.23.0 -> v0.36.0
golang.org/x/time	v0.8.0 -> v0.15.0
golang.org/x/tools	v0.31.0 -> v0.43.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
github.com/labstack/echo/v4	v4.13.3 → v4.15.3

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Echo: Encoded slash (%2F) bypasses route-level protection and exposes static files

CVE-2026-55677 / GHSA-vfp3-v2gw-7wfq

More information

Details

Summary

Echo's router and static file handler disagree on URL path decoding. The router matches routes using the raw encoded path (preserving %2F as-is), while StaticDirectoryHandler unescapes %2F to / before resolving filesystem paths. This allows an attacker to bypass route-level access controls and read static files without authorization.

Details

Root cause 1 — router.go lines 798-802:
The router uses req.URL.RawPath for route matching when useEscapedPathForRouting is false (the default). This means /admin%2Fsecret.txt is treated as a single path segment and does NOT match the /admin/* route pattern.

if!r.useEscapedPathForRouting&&req.URL.RawPath!="" {
path=req.URL.RawPath
}

Root cause 2 — echo.go lines 559-568:
StaticDirectoryHandler calls url.PathUnescape() on the path parameter before opening files. This converts %2F back to /, resolving admin/secret.txt on disk.

if!disablePathUnescaping {
tmpPath, err:=url.PathUnescape(p)
p=tmpPath
}
name:=filepath.ToSlash(filepath.Clean(strings.TrimPrefix(p, "/")))

PoC (Screenshot)

Sample:

403:

Bypass with encoded slash:

Impact

Unauthorized static file disclosure. Applications that protect route prefixes with authentication middleware while also serving static files from a broader root are vulnerable. An attacker only needs to encode the slash (/ → %2F) in the URL to bypass all route-level protection.

Common affected pattern:

adminGroup:=e.Group("/admin", authMiddleware)
e.StaticFS("/", os.DirFS("public"))

Severity

• CVSS Score: 7.5 / 10 (High)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

References

• https://github.com/labstack/echo/security/advisories/GHSA-vfp3-v2gw-7wfq
• https://nvd.nist.gov/vuln/detail/CVE-2026-55677
• https://github.com/labstack/echo/pull/3009
• https://github.com/labstack/echo/pull/3011
• https://github.com/labstack/echo/commit/8d1ae9d3360a71672418856d58753af25f2c3986
• https://github.com/labstack/echo/commit/c3fa2a27ff92b2b8db360de614f999ef1da24725
• https://github.com/labstack/echo/releases/tag/v4.15.3
• https://github.com/labstack/echo/releases/tag/v5.2.0
• https://github.com/advisories/GHSA-vfp3-v2gw-7wfq

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

labstack/echo (github.com/labstack/echo/v4)

v4.15.3: - Static encoded-separator route bypass fix (GHSA-vfp3-v2gw-7wfq)

Compare Source

Security

• fix(static): reject encoded path separators that bypass route-level middleware by @​vishr in #​3011

Fixes GHSA-vfp3-v2gw-7wfq: an encoded path separator (%2F or %5C) in a static file URL could bypass route-level middleware (e.g. authentication on a sibling route) and disclose static files. Both StaticDirectoryHandler (used by Static/StaticFS) and the Static middleware are affected. Backport of the v5 fix (#​3009, released in v5.2.0). Thanks to @​a-tt-om and @​oran-gugu for reporting.

Full Changelog: labstack/echo@v4.15.2...v4.15.3

v4.15.2: - Context.Scheme() header validation

Compare Source

Security

• Context.Scheme() should validate values taken from header by @​aldas in #​2962

Thanks to @​shblue21 for reporting this issue.

Full Changelog: labstack/echo@v4.15.1...v4.15.2

v4.15.1

Compare Source

What's Changed

• CSRF: support older token-based CSRF protection handler that want to render token into template by @​aldas in #​2905

Full Changelog: labstack/echo@v4.15.0...v4.15.1

v4.15.0

Compare Source

Security

NB: If your application relies on cross-origin or same-site (same subdomain) requests do not blindly push this version to production

The CSRF middleware now supports the Sec-Fetch-Site header as a modern, defense-in-depth approach to CSRF
protection, implementing the OWASP-recommended Fetch Metadata API alongside the traditional token-based mechanism.

How it works:

Modern browsers automatically send the Sec-Fetch-Site header with all requests, indicating the relationship
between the request origin and the target. The middleware uses this to make security decisions:

• same-origin or none: Requests are allowed (exact origin match or direct user navigation)
• same-site: Falls back to token validation (e.g., subdomain to main domain)
• cross-site: Blocked by default with 403 error for unsafe methods (POST, PUT, DELETE, PATCH)

For browsers that don't send this header (older browsers), the middleware seamlessly falls back to
traditional token-based CSRF protection.

New Configuration Options:

• TrustedOrigins []string: Allowlist specific origins for cross-site requests (useful for OAuth callbacks, webhooks)
• AllowSecFetchSiteFunc func(echo.Context) (bool, error): Custom logic for same-site/cross-site request validation

Example:

e.Use(middleware.CSRFWithConfig(middleware.CSRFConfig{
// Allow OAuth callbacks from trusted providerTrustedOrigins: []string{"https://oauth-provider.com"},
// Custom validation for same-site requestsAllowSecFetchSiteFunc: func(c echo.Context) (bool, error) {
// Your custom authorization logic herereturnvalidateCustomAuth(c), nil// return true, err // blocks request with error// return true, nil // allows CSRF request through// return false, nil // falls back to legacy token logic
},
}))

PR: #​2858

Type-Safe Generic Parameter Binding

• Added generic functions for type-safe parameter extraction and context access by @​aldas in #​2856

  Echo now provides generic functions for extracting path, query, and form parameters with automatic type conversion,
  eliminating manual string parsing and type assertions.

  New Functions:

  • Path parameters: PathParam[T], PathParamOr[T]
  • Query parameters: QueryParam[T], QueryParamOr[T], QueryParams[T], QueryParamsOr[T]
  • Form values: FormParam[T], FormParamOr[T], FormParams[T], FormParamsOr[T]
  • Context store: ContextGet[T], ContextGetOr[T]

  Supported Types:
  Primitives (bool, string, int/uint variants, float32/float64), time.Duration, time.Time
  (with custom layouts and Unix timestamp support), and custom types implementing BindUnmarshaler,
  TextUnmarshaler, or JSONUnmarshaler.

  Example:

  // Before: Manual parsingidStr:=c.Param("id")
  id, err:=strconv.Atoi(idStr)
  // After: Type-safe with automatic parsingid, err:=echo.PathParam[int](c, "id")
  // With default valuespage, err:=echo.QueryParamOr[int](c, "page", 1)
  limit, err:=echo.QueryParamOr[int](c, "limit", 20)
  // Type-safe context access (no more panics from type assertions)user, err:=echo.ContextGet[*User](c, "user")

PR: #​2856

DEPRECATION NOTICE Timeout Middleware Deprecated - Use ContextTimeout Instead

The middleware.Timeout middleware has been deprecated due to fundamental architectural issues that cause
data races. Use middleware.ContextTimeout or middleware.ContextTimeoutWithConfig instead.

Why is this being deprecated?

The Timeout middleware manipulates response writers across goroutine boundaries, which causes data races that
cannot be reliably fixed without a complete architectural redesign. The middleware:

• Swaps the response writer using http.TimeoutHandler
• Must be the first middleware in the chain (fragile constraint)
• Can cause races with other middleware (Logger, metrics, custom middleware)
• Has been the source of multiple race condition fixes over the years

What should you use instead?

The ContextTimeout middleware (available since v4.12.0) provides timeout functionality using Go's standard
context mechanism. It is:

• Race-free by design
• Can be placed anywhere in the middleware chain
• Simpler and more maintainable
• Compatible with all other middleware

Migration Guide:

// Before (deprecated):e.Use(middleware.Timeout())
// After (recommended):e.Use(middleware.ContextTimeout(30*time.Second))

Important Behavioral Differences:

1. Handler cooperation required: With ContextTimeout, your handlers must check context.Done() for cooperative
   cancellation. The old Timeout middleware would send a 503 response regardless of handler cooperation, but had
   data race issues.

2. Error handling: ContextTimeout returns errors through the standard error handling flow. Handlers that receive
   context.DeadlineExceeded should handle it appropriately:

e.GET("/long-task", func(c echo.Context) error {
ctx:=c.Request().Context()
// Example: database query with contextresult, err:=db.QueryContext(ctx, "SELECT * FROM large_table")
iferr!=nil {
iferrors.Is(err, context.DeadlineExceeded) {
// Handle timeoutreturnecho.NewHTTPError(http.StatusServiceUnavailable, "Request timeout")
}
returnerr
}
returnc.JSON(http.StatusOK, result)
})

3. Background tasks: For long-running background tasks, use goroutines with context:

e.GET("/async-task", func(c echo.Context) error {
ctx:=c.Request().Context()
resultCh:=make(chanResult, 1)
errCh:=make(chanerror, 1)
gofunc() {
result, err:=performLongTask(ctx)
iferr!=nil {
errCh<-errreturn
}
resultCh<-result
}()
select {
caseresult:=<-resultCh:
returnc.JSON(http.StatusOK, result)
caseerr:=<-errCh:
returnerrcase<-ctx.Done():
returnecho.NewHTTPError(http.StatusServiceUnavailable, "Request timeout")
}
})

Enhancements

• Fixes by @​aldas in #​2852
• Generic functions by @​aldas in #​2856
• CRSF with Sec-Fetch-Site checks by @​aldas in #​2858

v4.14.0

Compare Source

middleware.Logger has been deprecated. For request logging, use middleware.RequestLogger or
middleware.RequestLoggerWithConfig.

middleware.RequestLogger replaces middleware.Logger, offering comparable configuration while relying on the
Go standard library’s new slog logger.

The previous default output format was JSON. The new default follows the standard slog logger settings.
To continue emitting request logs in JSON, configure slog accordingly:

slog.SetDefault(slog.New(slog.NewJSONHandler(os.Stdout, nil)))
e.Use(middleware.RequestLogger())

Security

• Logger middleware json string escaping and deprecation by @​aldas in #​2849

Enhancements

• Update deps by @​aldas in #​2807
• refactor to use reflect.TypeFor by @​cuiweixie in #​2812
• Use Go 1.25 in CI by @​aldas in #​2810
• Modernize context.go by replacing interface{} with any by @​vishr in #​2822
• Fix typo in SetParamValues comment by @​vishr in #​2828
• Fix typo in ContextTimeout middleware comment by @​vishr in #​2827
• Improve BasicAuth middleware: use strings.Cut and RFC compliance by @​vishr in #​2825
• Fix duplicate plus operator in router backtracking logic by @​yuya-morimoto in #​2832
• Replace custom private IP range check with built-in net.IP.IsPrivate by @​kumapower17 in #​2835
• Ensure proxy connection is closed in proxyRaw function(#​2837) by @​kumapower17 in #​2838
• Update deps by @​aldas in #​2843
• Update golang.org/x/* deps by @​aldas in #​2850

v4.13.4

Compare Source

Enhancements

• chore: fix some typos in comment by @​zhuhaicity in #​2735
• CI: test with Go 1.24 by @​aldas in #​2748
• Add support for TLS WebSocket proxy by @​t-ibayashi-safie in #​2762

Security

• Update dependencies for GO-2025-3487, GO-2025-3503 and GO-2025-3595 in #​2780

---

Configuration

📅 Schedule: (in timezone Asia/Tokyo)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

ℹ️ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 12 additional dependencies were updated
• The go directive was updated for compatibility reasons

Details:

Package	Change
go	1.24.2 -> 1.25.0
github.com/stretchr/testify	v1.10.0 -> v1.11.1
github.com/labstack/gommon	v0.4.2 -> v0.5.0
github.com/mattn/go-colorable	v0.1.13 -> v0.1.14
github.com/mattn/go-isatty	v0.0.20 -> v0.0.22
golang.org/x/crypto	v0.36.0 -> v0.50.0
golang.org/x/mod	v0.24.0 -> v0.34.0
golang.org/x/net	v0.37.0 -> v0.53.0
golang.org/x/sync	v0.13.0 -> v0.20.0
golang.org/x/sys	v0.31.0 -> v0.43.0
golang.org/x/text	v0.23.0 -> v0.36.0
golang.org/x/time	v0.8.0 -> v0.15.0
golang.org/x/tools	v0.31.0 -> v0.43.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
github.com/labstack/echo/v4	v4.13.3 → v4.15.3

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Echo: Encoded slash (%2F) bypasses route-level protection and exposes static files

CVE-2026-55677 / GHSA-vfp3-v2gw-7wfq

More information

Details

Summary

Echo's router and static file handler disagree on URL path decoding. The router matches routes using the raw encoded path (preserving %2F as-is), while StaticDirectoryHandler unescapes %2F to / before resolving filesystem paths. This allows an attacker to bypass route-level access controls and read static files without authorization.

Details

Root cause 1 — router.go lines 798-802:
The router uses req.URL.RawPath for route matching when useEscapedPathForRouting is false (the default). This means /admin%2Fsecret.txt is treated as a single path segment and does NOT match the /admin/* route pattern.

if!r.useEscapedPathForRouting&&req.URL.RawPath!="" {
path=req.URL.RawPath
}

Root cause 2 — echo.go lines 559-568:
StaticDirectoryHandler calls url.PathUnescape() on the path parameter before opening files. This converts %2F back to /, resolving admin/secret.txt on disk.

if!disablePathUnescaping {
tmpPath, err:=url.PathUnescape(p)
p=tmpPath
}
name:=filepath.ToSlash(filepath.Clean(strings.TrimPrefix(p, "/")))

PoC (Screenshot)

Sample:

403:

Bypass with encoded slash:

Impact

Unauthorized static file disclosure. Applications that protect route prefixes with authentication middleware while also serving static files from a broader root are vulnerable. An attacker only needs to encode the slash (/ → %2F) in the URL to bypass all route-level protection.

Common affected pattern:

adminGroup:=e.Group("/admin", authMiddleware)
e.StaticFS("/", os.DirFS("public"))

Severity

• CVSS Score: 7.5 / 10 (High)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

References

• https://github.com/labstack/echo/security/advisories/GHSA-vfp3-v2gw-7wfq
• https://nvd.nist.gov/vuln/detail/CVE-2026-55677
• https://github.com/labstack/echo/pull/3009
• https://github.com/labstack/echo/pull/3011
• https://github.com/labstack/echo/commit/8d1ae9d3360a71672418856d58753af25f2c3986
• https://github.com/labstack/echo/commit/c3fa2a27ff92b2b8db360de614f999ef1da24725
• https://github.com/labstack/echo/releases/tag/v4.15.3
• https://github.com/labstack/echo/releases/tag/v5.2.0
• https://github.com/advisories/GHSA-vfp3-v2gw-7wfq

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

labstack/echo (github.com/labstack/echo/v4)

v4.15.3: - Static encoded-separator route bypass fix (GHSA-vfp3-v2gw-7wfq)

Compare Source

Security

• fix(static): reject encoded path separators that bypass route-level middleware by @​vishr in #​3011

Fixes GHSA-vfp3-v2gw-7wfq: an encoded path separator (%2F or %5C) in a static file URL could bypass route-level middleware (e.g. authentication on a sibling route) and disclose static files. Both StaticDirectoryHandler (used by Static/StaticFS) and the Static middleware are affected. Backport of the v5 fix (#​3009, released in v5.2.0). Thanks to @​a-tt-om and @​oran-gugu for reporting.

Full Changelog: labstack/echo@v4.15.2...v4.15.3

v4.15.2: - Context.Scheme() header validation

Compare Source

Security

• Context.Scheme() should validate values taken from header by @​aldas in #​2962

Thanks to @​shblue21 for reporting this issue.

Full Changelog: labstack/echo@v4.15.1...v4.15.2

v4.15.1

Compare Source

What's Changed

• CSRF: support older token-based CSRF protection handler that want to render token into template by @​aldas in #​2905

Full Changelog: labstack/echo@v4.15.0...v4.15.1

v4.15.0

Compare Source

Security

NB: If your application relies on cross-origin or same-site (same subdomain) requests do not blindly push this version to production

The CSRF middleware now supports the Sec-Fetch-Site header as a modern, defense-in-depth approach to CSRF
protection, implementing the OWASP-recommended Fetch Metadata API alongside the traditional token-based mechanism.

How it works:

Modern browsers automatically send the Sec-Fetch-Site header with all requests, indicating the relationship
between the request origin and the target. The middleware uses this to make security decisions:

• same-origin or none: Requests are allowed (exact origin match or direct user navigation)
• same-site: Falls back to token validation (e.g., subdomain to main domain)
• cross-site: Blocked by default with 403 error for unsafe methods (POST, PUT, DELETE, PATCH)

For browsers that don't send this header (older browsers), the middleware seamlessly falls back to
traditional token-based CSRF protection.

New Configuration Options:

• TrustedOrigins []string: Allowlist specific origins for cross-site requests (useful for OAuth callbacks, webhooks)
• AllowSecFetchSiteFunc func(echo.Context) (bool, error): Custom logic for same-site/cross-site request validation

Example:

e.Use(middleware.CSRFWithConfig(middleware.CSRFConfig{
// Allow OAuth callbacks from trusted providerTrustedOrigins: []string{"https://oauth-provider.com"},
// Custom validation for same-site requestsAllowSecFetchSiteFunc: func(c echo.Context) (bool, error) {
// Your custom authorization logic herereturnvalidateCustomAuth(c), nil// return true, err // blocks request with error// return true, nil // allows CSRF request through// return false, nil // falls back to legacy token logic
},
}))

PR: #​2858

Type-Safe Generic Parameter Binding

• Added generic functions for type-safe parameter extraction and context access by @​aldas in #​2856

  Echo now provides generic functions for extracting path, query, and form parameters with automatic type conversion,
  eliminating manual string parsing and type assertions.

  New Functions:

  • Path parameters: PathParam[T], PathParamOr[T]
  • Query parameters: QueryParam[T], QueryParamOr[T], QueryParams[T], QueryParamsOr[T]
  • Form values: FormParam[T], FormParamOr[T], FormParams[T], FormParamsOr[T]
  • Context store: ContextGet[T], ContextGetOr[T]

  Supported Types:
  Primitives (bool, string, int/uint variants, float32/float64), time.Duration, time.Time
  (with custom layouts and Unix timestamp support), and custom types implementing BindUnmarshaler,
  TextUnmarshaler, or JSONUnmarshaler.

  Example:

  // Before: Manual parsingidStr:=c.Param("id")
  id, err:=strconv.Atoi(idStr)
  // After: Type-safe with automatic parsingid, err:=echo.PathParam[int](c, "id")
  // With default valuespage, err:=echo.QueryParamOr[int](c, "page", 1)
  limit, err:=echo.QueryParamOr[int](c, "limit", 20)
  // Type-safe context access (no more panics from type assertions)user, err:=echo.ContextGet[*User](c, "user")

PR: #​2856

DEPRECATION NOTICE Timeout Middleware Deprecated - Use ContextTimeout Instead

The middleware.Timeout middleware has been deprecated due to fundamental architectural issues that cause
data races. Use middleware.ContextTimeout or middleware.ContextTimeoutWithConfig instead.

Why is this being deprecated?

The Timeout middleware manipulates response writers across goroutine boundaries, which causes data races that
cannot be reliably fixed without a complete architectural redesign. The middleware:

• Swaps the response writer using http.TimeoutHandler
• Must be the first middleware in the chain (fragile constraint)
• Can cause races with other middleware (Logger, metrics, custom middleware)
• Has been the source of multiple race condition fixes over the years

What should you use instead?

The ContextTimeout middleware (available since v4.12.0) provides timeout functionality using Go's standard
context mechanism. It is:

• Race-free by design
• Can be placed anywhere in the middleware chain
• Simpler and more maintainable
• Compatible with all other middleware

Migration Guide:

// Before (deprecated):e.Use(middleware.Timeout())
// After (recommended):e.Use(middleware.ContextTimeout(30*time.Second))

Important Behavioral Differences:

1. Handler cooperation required: With ContextTimeout, your handlers must check context.Done() for cooperative
   cancellation. The old Timeout middleware would send a 503 response regardless of handler cooperation, but had
   data race issues.

2. Error handling: ContextTimeout returns errors through the standard error handling flow. Handlers that receive
   context.DeadlineExceeded should handle it appropriately:

e.GET("/long-task", func(c echo.Context) error {
ctx:=c.Request().Context()
// Example: database query with contextresult, err:=db.QueryContext(ctx, "SELECT * FROM large_table")
iferr!=nil {
iferrors.Is(err, context.DeadlineExceeded) {
// Handle timeoutreturnecho.NewHTTPError(http.StatusServiceUnavailable, "Request timeout")
}
returnerr
}
returnc.JSON(http.StatusOK, result)
})

3. Background tasks: For long-running background tasks, use goroutines with context:

e.GET("/async-task", func(c echo.Context) error {
ctx:=c.Request().Context()
resultCh:=make(chanResult, 1)
errCh:=make(chanerror, 1)
gofunc() {
result, err:=performLongTask(ctx)
iferr!=nil {
errCh<-errreturn
}
resultCh<-result
}()
select {
caseresult:=<-resultCh:
returnc.JSON(http.StatusOK, result)
caseerr:=<-errCh:
returnerrcase<-ctx.Done():
returnecho.NewHTTPError(http.StatusServiceUnavailable, "Request timeout")
}
})

Enhancements

• Fixes by @​aldas in #​2852
• Generic functions by @​aldas in #​2856
• CRSF with Sec-Fetch-Site checks by @​aldas in #​2858

v4.14.0

Compare Source

middleware.Logger has been deprecated. For request logging, use middleware.RequestLogger or
middleware.RequestLoggerWithConfig.

middleware.RequestLogger replaces middleware.Logger, offering comparable configuration while relying on the
Go standard library’s new slog logger.

The previous default output format was JSON. The new default follows the standard slog logger settings.
To continue emitting request logs in JSON, configure slog accordingly:

slog.SetDefault(slog.New(slog.NewJSONHandler(os.Stdout, nil)))
e.Use(middleware.RequestLogger())

Security

• Logger middleware json string escaping and deprecation by @​aldas in #​2849

Enhancements

• Update deps by @​aldas in #​2807
• refactor to use reflect.TypeFor by @​cuiweixie in #​2812
• Use Go 1.25 in CI by @​aldas in #​2810
• Modernize context.go by replacing interface{} with any by @​vishr in #​2822
• Fix typo in SetParamValues comment by @​vishr in #​2828
• Fix typo in ContextTimeout middleware comment by @​vishr in #​2827
• Improve BasicAuth middleware: use strings.Cut and RFC compliance by @​vishr in #​2825
• Fix duplicate plus operator in router backtracking logic by @​yuya-morimoto in #​2832
• Replace custom private IP range check with built-in net.IP.IsPrivate by @​kumapower17 in #​2835
• Ensure proxy connection is closed in proxyRaw function(#​2837) by @​kumapower17 in #​2838
• Update deps by @​aldas in #​2843
• Update golang.org/x/* deps by @​aldas in #​2850

v4.13.4

Compare Source

Enhancements

• chore: fix some typos in comment by @​zhuhaicity in #​2735
• CI: test with Go 1.24 by @​aldas in #​2748
• Add support for TLS WebSocket proxy by @​t-ibayashi-safie in #​2762

Security

• Update dependencies for GO-2025-3487, GO-2025-3503 and GO-2025-3595 in #​2780

---

Configuration

📅 Schedule: (in timezone Asia/Tokyo)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

ℹ️ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 12 additional dependencies were updated
• The go directive was updated for compatibility reasons

Details:

Package	Change
go	1.24.2 -> 1.25.0
github.com/stretchr/testify	v1.10.0 -> v1.11.1
github.com/labstack/gommon	v0.4.2 -> v0.5.0
github.com/mattn/go-colorable	v0.1.13 -> v0.1.14
github.com/mattn/go-isatty	v0.0.20 -> v0.0.22
golang.org/x/crypto	v0.36.0 -> v0.50.0
golang.org/x/mod	v0.24.0 -> v0.34.0
golang.org/x/net	v0.37.0 -> v0.53.0
golang.org/x/sync	v0.13.0 -> v0.20.0
golang.org/x/sys	v0.31.0 -> v0.43.0
golang.org/x/text	v0.23.0 -> v0.36.0
golang.org/x/time	v0.8.0 -> v0.15.0
golang.org/x/tools	v0.31.0 -> v0.43.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
github.com/labstack/echo/v4	v4.13.3 → v4.15.3

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Echo: Encoded slash (%2F) bypasses route-level protection and exposes static files

CVE-2026-55677 / GHSA-vfp3-v2gw-7wfq

More information

Details

Summary

Echo's router and static file handler disagree on URL path decoding. The router matches routes using the raw encoded path (preserving %2F as-is), while StaticDirectoryHandler unescapes %2F to / before resolving filesystem paths. This allows an attacker to bypass route-level access controls and read static files without authorization.

Details

Root cause 1 — router.go lines 798-802:
The router uses req.URL.RawPath for route matching when useEscapedPathForRouting is false (the default). This means /admin%2Fsecret.txt is treated as a single path segment and does NOT match the /admin/* route pattern.

if!r.useEscapedPathForRouting&&req.URL.RawPath!="" {
path=req.URL.RawPath
}

Root cause 2 — echo.go lines 559-568:
StaticDirectoryHandler calls url.PathUnescape() on the path parameter before opening files. This converts %2F back to /, resolving admin/secret.txt on disk.

if!disablePathUnescaping {
tmpPath, err:=url.PathUnescape(p)
p=tmpPath
}
name:=filepath.ToSlash(filepath.Clean(strings.TrimPrefix(p, "/")))

PoC (Screenshot)

Sample:

403:

Bypass with encoded slash:

Impact

Unauthorized static file disclosure. Applications that protect route prefixes with authentication middleware while also serving static files from a broader root are vulnerable. An attacker only needs to encode the slash (/ → %2F) in the URL to bypass all route-level protection.

Common affected pattern:

adminGroup:=e.Group("/admin", authMiddleware)
e.StaticFS("/", os.DirFS("public"))

Severity

• CVSS Score: 7.5 / 10 (High)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

References

• https://github.com/labstack/echo/security/advisories/GHSA-vfp3-v2gw-7wfq
• https://nvd.nist.gov/vuln/detail/CVE-2026-55677
• https://github.com/labstack/echo/pull/3009
• https://github.com/labstack/echo/pull/3011
• https://github.com/labstack/echo/commit/8d1ae9d3360a71672418856d58753af25f2c3986
• https://github.com/labstack/echo/commit/c3fa2a27ff92b2b8db360de614f999ef1da24725
• https://github.com/labstack/echo/releases/tag/v4.15.3
• https://github.com/labstack/echo/releases/tag/v5.2.0
• https://github.com/advisories/GHSA-vfp3-v2gw-7wfq

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

labstack/echo (github.com/labstack/echo/v4)

v4.15.3: - Static encoded-separator route bypass fix (GHSA-vfp3-v2gw-7wfq)

Compare Source

Security

• fix(static): reject encoded path separators that bypass route-level middleware by @​vishr in #​3011

Fixes GHSA-vfp3-v2gw-7wfq: an encoded path separator (%2F or %5C) in a static file URL could bypass route-level middleware (e.g. authentication on a sibling route) and disclose static files. Both StaticDirectoryHandler (used by Static/StaticFS) and the Static middleware are affected. Backport of the v5 fix (#​3009, released in v5.2.0). Thanks to @​a-tt-om and @​oran-gugu for reporting.

Full Changelog: labstack/echo@v4.15.2...v4.15.3

v4.15.2: - Context.Scheme() header validation

Compare Source

Security

• Context.Scheme() should validate values taken from header by @​aldas in #​2962

Thanks to @​shblue21 for reporting this issue.

Full Changelog: labstack/echo@v4.15.1...v4.15.2

v4.15.1

Compare Source

What's Changed

• CSRF: support older token-based CSRF protection handler that want to render token into template by @​aldas in #​2905

Full Changelog: labstack/echo@v4.15.0...v4.15.1

v4.15.0

Compare Source

Security

NB: If your application relies on cross-origin or same-site (same subdomain) requests do not blindly push this version to production

The CSRF middleware now supports the Sec-Fetch-Site header as a modern, defense-in-depth approach to CSRF
protection, implementing the OWASP-recommended Fetch Metadata API alongside the traditional token-based mechanism.

How it works:

Modern browsers automatically send the Sec-Fetch-Site header with all requests, indicating the relationship
between the request origin and the target. The middleware uses this to make security decisions:

• same-origin or none: Requests are allowed (exact origin match or direct user navigation)
• same-site: Falls back to token validation (e.g., subdomain to main domain)
• cross-site: Blocked by default with 403 error for unsafe methods (POST, PUT, DELETE, PATCH)

For browsers that don't send this header (older browsers), the middleware seamlessly falls back to
traditional token-based CSRF protection.

New Configuration Options:

• TrustedOrigins []string: Allowlist specific origins for cross-site requests (useful for OAuth callbacks, webhooks)
• AllowSecFetchSiteFunc func(echo.Context) (bool, error): Custom logic for same-site/cross-site request validation

Example:

e.Use(middleware.CSRFWithConfig(middleware.CSRFConfig{
// Allow OAuth callbacks from trusted providerTrustedOrigins: []string{"https://oauth-provider.com"},
// Custom validation for same-site requestsAllowSecFetchSiteFunc: func(c echo.Context) (bool, error) {
// Your custom authorization logic herereturnvalidateCustomAuth(c), nil// return true, err // blocks request with error// return true, nil // allows CSRF request through// return false, nil // falls back to legacy token logic
},
}))

PR: #​2858

Type-Safe Generic Parameter Binding

• Added generic functions for type-safe parameter extraction and context access by @​aldas in #​2856

  Echo now provides generic functions for extracting path, query, and form parameters with automatic type conversion,
  eliminating manual string parsing and type assertions.

  New Functions:

  • Path parameters: PathParam[T], PathParamOr[T]
  • Query parameters: QueryParam[T], QueryParamOr[T], QueryParams[T], QueryParamsOr[T]
  • Form values: FormParam[T], FormParamOr[T], FormParams[T], FormParamsOr[T]
  • Context store: ContextGet[T], ContextGetOr[T]

  Supported Types:
  Primitives (bool, string, int/uint variants, float32/float64), time.Duration, time.Time
  (with custom layouts and Unix timestamp support), and custom types implementing BindUnmarshaler,
  TextUnmarshaler, or JSONUnmarshaler.

  Example:

  // Before: Manual parsingidStr:=c.Param("id")
  id, err:=strconv.Atoi(idStr)
  // After: Type-safe with automatic parsingid, err:=echo.PathParam[int](c, "id")
  // With default valuespage, err:=echo.QueryParamOr[int](c, "page", 1)
  limit, err:=echo.QueryParamOr[int](c, "limit", 20)
  // Type-safe context access (no more panics from type assertions)user, err:=echo.ContextGet[*User](c, "user")

PR: #​2856

DEPRECATION NOTICE Timeout Middleware Deprecated - Use ContextTimeout Instead

The middleware.Timeout middleware has been deprecated due to fundamental architectural issues that cause
data races. Use middleware.ContextTimeout or middleware.ContextTimeoutWithConfig instead.

Why is this being deprecated?

The Timeout middleware manipulates response writers across goroutine boundaries, which causes data races that
cannot be reliably fixed without a complete architectural redesign. The middleware:

• Swaps the response writer using http.TimeoutHandler
• Must be the first middleware in the chain (fragile constraint)
• Can cause races with other middleware (Logger, metrics, custom middleware)
• Has been the source of multiple race condition fixes over the years

What should you use instead?

The ContextTimeout middleware (available since v4.12.0) provides timeout functionality using Go's standard
context mechanism. It is:

• Race-free by design
• Can be placed anywhere in the middleware chain
• Simpler and more maintainable
• Compatible with all other middleware

Migration Guide:

// Before (deprecated):e.Use(middleware.Timeout())
// After (recommended):e.Use(middleware.ContextTimeout(30*time.Second))

Important Behavioral Differences:

1. Handler cooperation required: With ContextTimeout, your handlers must check context.Done() for cooperative
   cancellation. The old Timeout middleware would send a 503 response regardless of handler cooperation, but had
   data race issues.

2. Error handling: ContextTimeout returns errors through the standard error handling flow. Handlers that receive
   context.DeadlineExceeded should handle it appropriately:

e.GET("/long-task", func(c echo.Context) error {
ctx:=c.Request().Context()
// Example: database query with contextresult, err:=db.QueryContext(ctx, "SELECT * FROM large_table")
iferr!=nil {
iferrors.Is(err, context.DeadlineExceeded) {
// Handle timeoutreturnecho.NewHTTPError(http.StatusServiceUnavailable, "Request timeout")
}
returnerr
}
returnc.JSON(http.StatusOK, result)
})

3. Background tasks: For long-running background tasks, use goroutines with context:

e.GET("/async-task", func(c echo.Context) error {
ctx:=c.Request().Context()
resultCh:=make(chanResult, 1)
errCh:=make(chanerror, 1)
gofunc() {
result, err:=performLongTask(ctx)
iferr!=nil {
errCh<-errreturn
}
resultCh<-result
}()
select {
caseresult:=<-resultCh:
returnc.JSON(http.StatusOK, result)
caseerr:=<-errCh:
returnerrcase<-ctx.Done():
returnecho.NewHTTPError(http.StatusServiceUnavailable, "Request timeout")
}
})

Enhancements

• Fixes by @​aldas in #​2852
• Generic functions by @​aldas in #​2856
• CRSF with Sec-Fetch-Site checks by @​aldas in #​2858

v4.14.0

Compare Source

middleware.Logger has been deprecated. For request logging, use middleware.RequestLogger or
middleware.RequestLoggerWithConfig.

middleware.RequestLogger replaces middleware.Logger, offering comparable configuration while relying on the
Go standard library’s new slog logger.

The previous default output format was JSON. The new default follows the standard slog logger settings.
To continue emitting request logs in JSON, configure slog accordingly:

slog.SetDefault(slog.New(slog.NewJSONHandler(os.Stdout, nil)))
e.Use(middleware.RequestLogger())

Security

• Logger middleware json string escaping and deprecation by @​aldas in #​2849

Enhancements

• Update deps by @​aldas in #​2807
• refactor to use reflect.TypeFor by @​cuiweixie in #​2812
• Use Go 1.25 in CI by @​aldas in #​2810
• Modernize context.go by replacing interface{} with any by @​vishr in #​2822
• Fix typo in SetParamValues comment by @​vishr in #​2828
• Fix typo in ContextTimeout middleware comment by @​vishr in #​2827
• Improve BasicAuth middleware: use strings.Cut and RFC compliance by @​vishr in #​2825
• Fix duplicate plus operator in router backtracking logic by @​yuya-morimoto in #​2832
• Replace custom private IP range check with built-in net.IP.IsPrivate by @​kumapower17 in #​2835
• Ensure proxy connection is closed in proxyRaw function(#​2837) by @​kumapower17 in #​2838
• Update deps by @​aldas in #​2843
• Update golang.org/x/* deps by @​aldas in #​2850

v4.13.4

Compare Source

Enhancements

• chore: fix some typos in comment by @​zhuhaicity in #​2735
• CI: test with Go 1.24 by @​aldas in #​2748
• Add support for TLS WebSocket proxy by @​t-ibayashi-safie in #​2762

Security

• Update dependencies for GO-2025-3487, GO-2025-3503 and GO-2025-3595 in #​2780

---

Configuration

📅 Schedule: (in timezone Asia/Tokyo)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

ℹ️ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 12 additional dependencies were updated
• The go directive was updated for compatibility reasons

Details:

Package	Change
go	1.24.2 -> 1.25.0
github.com/stretchr/testify	v1.10.0 -> v1.11.1
github.com/labstack/gommon	v0.4.2 -> v0.5.0
github.com/mattn/go-colorable	v0.1.13 -> v0.1.14
github.com/mattn/go-isatty	v0.0.20 -> v0.0.22
golang.org/x/crypto	v0.36.0 -> v0.50.0
golang.org/x/mod	v0.24.0 -> v0.34.0
golang.org/x/net	v0.37.0 -> v0.53.0
golang.org/x/sync	v0.13.0 -> v0.20.0
golang.org/x/sys	v0.31.0 -> v0.43.0
golang.org/x/text	v0.23.0 -> v0.36.0
golang.org/x/time	v0.8.0 -> v0.15.0
golang.org/x/tools	v0.31.0 -> v0.43.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
github.com/labstack/echo/v4	v4.13.3 → v4.15.3

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Echo: Encoded slash (%2F) bypasses route-level protection and exposes static files

CVE-2026-55677 / GHSA-vfp3-v2gw-7wfq

More information

Details

Summary

Echo's router and static file handler disagree on URL path decoding. The router matches routes using the raw encoded path (preserving %2F as-is), while StaticDirectoryHandler unescapes %2F to / before resolving filesystem paths. This allows an attacker to bypass route-level access controls and read static files without authorization.

Details

Root cause 1 — router.go lines 798-802:
The router uses req.URL.RawPath for route matching when useEscapedPathForRouting is false (the default). This means /admin%2Fsecret.txt is treated as a single path segment and does NOT match the /admin/* route pattern.

if!r.useEscapedPathForRouting&&req.URL.RawPath!="" {
path=req.URL.RawPath
}

Root cause 2 — echo.go lines 559-568:
StaticDirectoryHandler calls url.PathUnescape() on the path parameter before opening files. This converts %2F back to /, resolving admin/secret.txt on disk.

if!disablePathUnescaping {
tmpPath, err:=url.PathUnescape(p)
p=tmpPath
}
name:=filepath.ToSlash(filepath.Clean(strings.TrimPrefix(p, "/")))

PoC (Screenshot)

Sample:

403:

Bypass with encoded slash:

Impact

Unauthorized static file disclosure. Applications that protect route prefixes with authentication middleware while also serving static files from a broader root are vulnerable. An attacker only needs to encode the slash (/ → %2F) in the URL to bypass all route-level protection.

Common affected pattern:

adminGroup:=e.Group("/admin", authMiddleware)
e.StaticFS("/", os.DirFS("public"))

Severity

• CVSS Score: 7.5 / 10 (High)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

References

• https://github.com/labstack/echo/security/advisories/GHSA-vfp3-v2gw-7wfq
• https://nvd.nist.gov/vuln/detail/CVE-2026-55677
• https://github.com/labstack/echo/pull/3009
• https://github.com/labstack/echo/pull/3011
• https://github.com/labstack/echo/commit/8d1ae9d3360a71672418856d58753af25f2c3986
• https://github.com/labstack/echo/commit/c3fa2a27ff92b2b8db360de614f999ef1da24725
• https://github.com/labstack/echo/releases/tag/v4.15.3
• https://github.com/labstack/echo/releases/tag/v5.2.0
• https://github.com/advisories/GHSA-vfp3-v2gw-7wfq

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

labstack/echo (github.com/labstack/echo/v4)

v4.15.3: - Static encoded-separator route bypass fix (GHSA-vfp3-v2gw-7wfq)

Compare Source

Security

• fix(static): reject encoded path separators that bypass route-level middleware by @​vishr in #​3011

Fixes GHSA-vfp3-v2gw-7wfq: an encoded path separator (%2F or %5C) in a static file URL could bypass route-level middleware (e.g. authentication on a sibling route) and disclose static files. Both StaticDirectoryHandler (used by Static/StaticFS) and the Static middleware are affected. Backport of the v5 fix (#​3009, released in v5.2.0). Thanks to @​a-tt-om and @​oran-gugu for reporting.

Full Changelog: labstack/echo@v4.15.2...v4.15.3

v4.15.2: - Context.Scheme() header validation

Compare Source

Security

• Context.Scheme() should validate values taken from header by @​aldas in #​2962

Thanks to @​shblue21 for reporting this issue.

Full Changelog: labstack/echo@v4.15.1...v4.15.2

v4.15.1

Compare Source

What's Changed

• CSRF: support older token-based CSRF protection handler that want to render token into template by @​aldas in #​2905

Full Changelog: labstack/echo@v4.15.0...v4.15.1

v4.15.0

Compare Source

Security

NB: If your application relies on cross-origin or same-site (same subdomain) requests do not blindly push this version to production

The CSRF middleware now supports the Sec-Fetch-Site header as a modern, defense-in-depth approach to CSRF
protection, implementing the OWASP-recommended Fetch Metadata API alongside the traditional token-based mechanism.

How it works:

Modern browsers automatically send the Sec-Fetch-Site header with all requests, indicating the relationship
between the request origin and the target. The middleware uses this to make security decisions:

• same-origin or none: Requests are allowed (exact origin match or direct user navigation)
• same-site: Falls back to token validation (e.g., subdomain to main domain)
• cross-site: Blocked by default with 403 error for unsafe methods (POST, PUT, DELETE, PATCH)

For browsers that don't send this header (older browsers), the middleware seamlessly falls back to
traditional token-based CSRF protection.

New Configuration Options:

• TrustedOrigins []string: Allowlist specific origins for cross-site requests (useful for OAuth callbacks, webhooks)
• AllowSecFetchSiteFunc func(echo.Context) (bool, error): Custom logic for same-site/cross-site request validation

Example:

e.Use(middleware.CSRFWithConfig(middleware.CSRFConfig{
// Allow OAuth callbacks from trusted providerTrustedOrigins: []string{"https://oauth-provider.com"},
// Custom validation for same-site requestsAllowSecFetchSiteFunc: func(c echo.Context) (bool, error) {
// Your custom authorization logic herereturnvalidateCustomAuth(c), nil// return true, err // blocks request with error// return true, nil // allows CSRF request through// return false, nil // falls back to legacy token logic
},
}))

PR: #​2858

Type-Safe Generic Parameter Binding

• Added generic functions for type-safe parameter extraction and context access by @​aldas in #​2856

  Echo now provides generic functions for extracting path, query, and form parameters with automatic type conversion,
  eliminating manual string parsing and type assertions.

  New Functions:

  • Path parameters: PathParam[T], PathParamOr[T]
  • Query parameters: QueryParam[T], QueryParamOr[T], QueryParams[T], QueryParamsOr[T]
  • Form values: FormParam[T], FormParamOr[T], FormParams[T], FormParamsOr[T]
  • Context store: ContextGet[T], ContextGetOr[T]

  Supported Types:
  Primitives (bool, string, int/uint variants, float32/float64), time.Duration, time.Time
  (with custom layouts and Unix timestamp support), and custom types implementing BindUnmarshaler,
  TextUnmarshaler, or JSONUnmarshaler.

  Example:

  // Before: Manual parsingidStr:=c.Param("id")
  id, err:=strconv.Atoi(idStr)
  // After: Type-safe with automatic parsingid, err:=echo.PathParam[int](c, "id")
  // With default valuespage, err:=echo.QueryParamOr[int](c, "page", 1)
  limit, err:=echo.QueryParamOr[int](c, "limit", 20)
  // Type-safe context access (no more panics from type assertions)user, err:=echo.ContextGet[*User](c, "user")

PR: #​2856

DEPRECATION NOTICE Timeout Middleware Deprecated - Use ContextTimeout Instead

The middleware.Timeout middleware has been deprecated due to fundamental architectural issues that cause
data races. Use middleware.ContextTimeout or middleware.ContextTimeoutWithConfig instead.

Why is this being deprecated?

The Timeout middleware manipulates response writers across goroutine boundaries, which causes data races that
cannot be reliably fixed without a complete architectural redesign. The middleware:

• Swaps the response writer using http.TimeoutHandler
• Must be the first middleware in the chain (fragile constraint)
• Can cause races with other middleware (Logger, metrics, custom middleware)
• Has been the source of multiple race condition fixes over the years

What should you use instead?

The ContextTimeout middleware (available since v4.12.0) provides timeout functionality using Go's standard
context mechanism. It is:

• Race-free by design
• Can be placed anywhere in the middleware chain
• Simpler and more maintainable
• Compatible with all other middleware

Migration Guide:

// Before (deprecated):e.Use(middleware.Timeout())
// After (recommended):e.Use(middleware.ContextTimeout(30*time.Second))

Important Behavioral Differences:

1. Handler cooperation required: With ContextTimeout, your handlers must check context.Done() for cooperative
   cancellation. The old Timeout middleware would send a 503 response regardless of handler cooperation, but had
   data race issues.

2. Error handling: ContextTimeout returns errors through the standard error handling flow. Handlers that receive
   context.DeadlineExceeded should handle it appropriately:

e.GET("/long-task", func(c echo.Context) error {
ctx:=c.Request().Context()
// Example: database query with contextresult, err:=db.QueryContext(ctx, "SELECT * FROM large_table")
iferr!=nil {
iferrors.Is(err, context.DeadlineExceeded) {
// Handle timeoutreturnecho.NewHTTPError(http.StatusServiceUnavailable, "Request timeout")
}
returnerr
}
returnc.JSON(http.StatusOK, result)
})

3. Background tasks: For long-running background tasks, use goroutines with context:

e.GET("/async-task", func(c echo.Context) error {
ctx:=c.Request().Context()
resultCh:=make(chanResult, 1)
errCh:=make(chanerror, 1)
gofunc() {
result, err:=performLongTask(ctx)
iferr!=nil {
errCh<-errreturn
}
resultCh<-result
}()
select {
caseresult:=<-resultCh:
returnc.JSON(http.StatusOK, result)
caseerr:=<-errCh:
returnerrcase<-ctx.Done():
returnecho.NewHTTPError(http.StatusServiceUnavailable, "Request timeout")
}
})

Enhancements

• Fixes by @​aldas in #​2852
• Generic functions by @​aldas in #​2856
• CRSF with Sec-Fetch-Site checks by @​aldas in #​2858

v4.14.0

Compare Source

middleware.Logger has been deprecated. For request logging, use middleware.RequestLogger or
middleware.RequestLoggerWithConfig.

middleware.RequestLogger replaces middleware.Logger, offering comparable configuration while relying on the
Go standard library’s new slog logger.

The previous default output format was JSON. The new default follows the standard slog logger settings.
To continue emitting request logs in JSON, configure slog accordingly:

slog.SetDefault(slog.New(slog.NewJSONHandler(os.Stdout, nil)))
e.Use(middleware.RequestLogger())

Security

• Logger middleware json string escaping and deprecation by @​aldas in #​2849

Enhancements

• Update deps by @​aldas in #​2807
• refactor to use reflect.TypeFor by @​cuiweixie in #​2812
• Use Go 1.25 in CI by @​aldas in #​2810
• Modernize context.go by replacing interface{} with any by @​vishr in #​2822
• Fix typo in SetParamValues comment by @​vishr in #​2828
• Fix typo in ContextTimeout middleware comment by @​vishr in #​2827
• Improve BasicAuth middleware: use strings.Cut and RFC compliance by @​vishr in #​2825
• Fix duplicate plus operator in router backtracking logic by @​yuya-morimoto in #​2832
• Replace custom private IP range check with built-in net.IP.IsPrivate by @​kumapower17 in #​2835
• Ensure proxy connection is closed in proxyRaw function(#​2837) by @​kumapower17 in #​2838
• Update deps by @​aldas in #​2843
• Update golang.org/x/* deps by @​aldas in #​2850

v4.13.4

Compare Source

Enhancements

• chore: fix some typos in comment by @​zhuhaicity in #​2735
• CI: test with Go 1.24 by @​aldas in #​2748
• Add support for TLS WebSocket proxy by @​t-ibayashi-safie in #​2762

Security

• Update dependencies for GO-2025-3487, GO-2025-3503 and GO-2025-3595 in #​2780

---

Configuration

📅 Schedule: (in timezone Asia/Tokyo)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

ℹ️ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 12 additional dependencies were updated
• The go directive was updated for compatibility reasons

Details:

Package	Change
go	1.24.2 -> 1.25.0
github.com/stretchr/testify	v1.10.0 -> v1.11.1
github.com/labstack/gommon	v0.4.2 -> v0.5.0
github.com/mattn/go-colorable	v0.1.13 -> v0.1.14
github.com/mattn/go-isatty	v0.0.20 -> v0.0.22
golang.org/x/crypto	v0.36.0 -> v0.50.0
golang.org/x/mod	v0.24.0 -> v0.34.0
golang.org/x/net	v0.37.0 -> v0.53.0
golang.org/x/sync	v0.13.0 -> v0.20.0
golang.org/x/sys	v0.31.0 -> v0.43.0
golang.org/x/text	v0.23.0 -> v0.36.0
golang.org/x/time	v0.8.0 -> v0.15.0
golang.org/x/tools	v0.31.0 -> v0.43.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
github.com/labstack/echo/v4	v4.13.3 → v4.15.3

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Echo: Encoded slash (%2F) bypasses route-level protection and exposes static files

CVE-2026-55677 / GHSA-vfp3-v2gw-7wfq

More information

Details

Summary

Echo's router and static file handler disagree on URL path decoding. The router matches routes using the raw encoded path (preserving %2F as-is), while StaticDirectoryHandler unescapes %2F to / before resolving filesystem paths. This allows an attacker to bypass route-level access controls and read static files without authorization.

Details

Root cause 1 — router.go lines 798-802:
The router uses req.URL.RawPath for route matching when useEscapedPathForRouting is false (the default). This means /admin%2Fsecret.txt is treated as a single path segment and does NOT match the /admin/* route pattern.

if!r.useEscapedPathForRouting&&req.URL.RawPath!="" {
path=req.URL.RawPath
}

Root cause 2 — echo.go lines 559-568:
StaticDirectoryHandler calls url.PathUnescape() on the path parameter before opening files. This converts %2F back to /, resolving admin/secret.txt on disk.

if!disablePathUnescaping {
tmpPath, err:=url.PathUnescape(p)
p=tmpPath
}
name:=filepath.ToSlash(filepath.Clean(strings.TrimPrefix(p, "/")))

PoC (Screenshot)

Sample:

403:

Bypass with encoded slash:

Impact

Unauthorized static file disclosure. Applications that protect route prefixes with authentication middleware while also serving static files from a broader root are vulnerable. An attacker only needs to encode the slash (/ → %2F) in the URL to bypass all route-level protection.

Common affected pattern:

adminGroup:=e.Group("/admin", authMiddleware)
e.StaticFS("/", os.DirFS("public"))

Severity

• CVSS Score: 7.5 / 10 (High)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

References

• https://github.com/labstack/echo/security/advisories/GHSA-vfp3-v2gw-7wfq
• https://nvd.nist.gov/vuln/detail/CVE-2026-55677
• https://github.com/labstack/echo/pull/3009
• https://github.com/labstack/echo/pull/3011
• https://github.com/labstack/echo/commit/8d1ae9d3360a71672418856d58753af25f2c3986
• https://github.com/labstack/echo/commit/c3fa2a27ff92b2b8db360de614f999ef1da24725
• https://github.com/labstack/echo/releases/tag/v4.15.3
• https://github.com/labstack/echo/releases/tag/v5.2.0
• https://github.com/advisories/GHSA-vfp3-v2gw-7wfq

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

labstack/echo (github.com/labstack/echo/v4)

v4.15.3: - Static encoded-separator route bypass fix (GHSA-vfp3-v2gw-7wfq)

Compare Source

Security

• fix(static): reject encoded path separators that bypass route-level middleware by @​vishr in #​3011

Fixes GHSA-vfp3-v2gw-7wfq: an encoded path separator (%2F or %5C) in a static file URL could bypass route-level middleware (e.g. authentication on a sibling route) and disclose static files. Both StaticDirectoryHandler (used by Static/StaticFS) and the Static middleware are affected. Backport of the v5 fix (#​3009, released in v5.2.0). Thanks to @​a-tt-om and @​oran-gugu for reporting.

Full Changelog: labstack/echo@v4.15.2...v4.15.3

v4.15.2: - Context.Scheme() header validation

Compare Source

Security

• Context.Scheme() should validate values taken from header by @​aldas in #​2962

Thanks to @​shblue21 for reporting this issue.

Full Changelog: labstack/echo@v4.15.1...v4.15.2

v4.15.1

Compare Source

What's Changed

• CSRF: support older token-based CSRF protection handler that want to render token into template by @​aldas in #​2905

Full Changelog: labstack/echo@v4.15.0...v4.15.1

v4.15.0

Compare Source

Security

NB: If your application relies on cross-origin or same-site (same subdomain) requests do not blindly push this version to production

The CSRF middleware now supports the Sec-Fetch-Site header as a modern, defense-in-depth approach to CSRF
protection, implementing the OWASP-recommended Fetch Metadata API alongside the traditional token-based mechanism.

How it works:

Modern browsers automatically send the Sec-Fetch-Site header with all requests, indicating the relationship
between the request origin and the target. The middleware uses this to make security decisions:

• same-origin or none: Requests are allowed (exact origin match or direct user navigation)
• same-site: Falls back to token validation (e.g., subdomain to main domain)
• cross-site: Blocked by default with 403 error for unsafe methods (POST, PUT, DELETE, PATCH)

For browsers that don't send this header (older browsers), the middleware seamlessly falls back to
traditional token-based CSRF protection.

New Configuration Options:

• TrustedOrigins []string: Allowlist specific origins for cross-site requests (useful for OAuth callbacks, webhooks)
• AllowSecFetchSiteFunc func(echo.Context) (bool, error): Custom logic for same-site/cross-site request validation

Example:

e.Use(middleware.CSRFWithConfig(middleware.CSRFConfig{
// Allow OAuth callbacks from trusted providerTrustedOrigins: []string{"https://oauth-provider.com"},
// Custom validation for same-site requestsAllowSecFetchSiteFunc: func(c echo.Context) (bool, error) {
// Your custom authorization logic herereturnvalidateCustomAuth(c), nil// return true, err // blocks request with error// return true, nil // allows CSRF request through// return false, nil // falls back to legacy token logic
},
}))

PR: #​2858

Type-Safe Generic Parameter Binding

• Added generic functions for type-safe parameter extraction and context access by @​aldas in #​2856

  Echo now provides generic functions for extracting path, query, and form parameters with automatic type conversion,
  eliminating manual string parsing and type assertions.

  New Functions:

  • Path parameters: PathParam[T], PathParamOr[T]
  • Query parameters: QueryParam[T], QueryParamOr[T], QueryParams[T], QueryParamsOr[T]
  • Form values: FormParam[T], FormParamOr[T], FormParams[T], FormParamsOr[T]
  • Context store: ContextGet[T], ContextGetOr[T]

  Supported Types:
  Primitives (bool, string, int/uint variants, float32/float64), time.Duration, time.Time
  (with custom layouts and Unix timestamp support), and custom types implementing BindUnmarshaler,
  TextUnmarshaler, or JSONUnmarshaler.

  Example:

  // Before: Manual parsingidStr:=c.Param("id")
  id, err:=strconv.Atoi(idStr)
  // After: Type-safe with automatic parsingid, err:=echo.PathParam[int](c, "id")
  // With default valuespage, err:=echo.QueryParamOr[int](c, "page", 1)
  limit, err:=echo.QueryParamOr[int](c, "limit", 20)
  // Type-safe context access (no more panics from type assertions)user, err:=echo.ContextGet[*User](c, "user")

PR: #​2856

DEPRECATION NOTICE Timeout Middleware Deprecated - Use ContextTimeout Instead

The middleware.Timeout middleware has been deprecated due to fundamental architectural issues that cause
data races. Use middleware.ContextTimeout or middleware.ContextTimeoutWithConfig instead.

Why is this being deprecated?

The Timeout middleware manipulates response writers across goroutine boundaries, which causes data races that
cannot be reliably fixed without a complete architectural redesign. The middleware:

• Swaps the response writer using http.TimeoutHandler
• Must be the first middleware in the chain (fragile constraint)
• Can cause races with other middleware (Logger, metrics, custom middleware)
• Has been the source of multiple race condition fixes over the years

What should you use instead?

The ContextTimeout middleware (available since v4.12.0) provides timeout functionality using Go's standard
context mechanism. It is:

• Race-free by design
• Can be placed anywhere in the middleware chain
• Simpler and more maintainable
• Compatible with all other middleware

Migration Guide:

// Before (deprecated):e.Use(middleware.Timeout())
// After (recommended):e.Use(middleware.ContextTimeout(30*time.Second))

Important Behavioral Differences:

1. Handler cooperation required: With ContextTimeout, your handlers must check context.Done() for cooperative
   cancellation. The old Timeout middleware would send a 503 response regardless of handler cooperation, but had
   data race issues.

2. Error handling: ContextTimeout returns errors through the standard error handling flow. Handlers that receive
   context.DeadlineExceeded should handle it appropriately:

e.GET("/long-task", func(c echo.Context) error {
ctx:=c.Request().Context()
// Example: database query with contextresult, err:=db.QueryContext(ctx, "SELECT * FROM large_table")
iferr!=nil {
iferrors.Is(err, context.DeadlineExceeded) {
// Handle timeoutreturnecho.NewHTTPError(http.StatusServiceUnavailable, "Request timeout")
}
returnerr
}
returnc.JSON(http.StatusOK, result)
})

3. Background tasks: For long-running background tasks, use goroutines with context:

e.GET("/async-task", func(c echo.Context) error {
ctx:=c.Request().Context()
resultCh:=make(chanResult, 1)
errCh:=make(chanerror, 1)
gofunc() {
result, err:=performLongTask(ctx)
iferr!=nil {
errCh<-errreturn
}
resultCh<-result
}()
select {
caseresult:=<-resultCh:
returnc.JSON(http.StatusOK, result)
caseerr:=<-errCh:
returnerrcase<-ctx.Done():
returnecho.NewHTTPError(http.StatusServiceUnavailable, "Request timeout")
}
})

Enhancements

• Fixes by @​aldas in #​2852
• Generic functions by @​aldas in #​2856
• CRSF with Sec-Fetch-Site checks by @​aldas in #​2858

v4.14.0

Compare Source

middleware.Logger has been deprecated. For request logging, use middleware.RequestLogger or
middleware.RequestLoggerWithConfig.

middleware.RequestLogger replaces middleware.Logger, offering comparable configuration while relying on the
Go standard library’s new slog logger.

The previous default output format was JSON. The new default follows the standard slog logger settings.
To continue emitting request logs in JSON, configure slog accordingly:

slog.SetDefault(slog.New(slog.NewJSONHandler(os.Stdout, nil)))
e.Use(middleware.RequestLogger())

Security

• Logger middleware json string escaping and deprecation by @​aldas in #​2849

Enhancements

• Update deps by @​aldas in #​2807
• refactor to use reflect.TypeFor by @​cuiweixie in #​2812
• Use Go 1.25 in CI by @​aldas in #​2810
• Modernize context.go by replacing interface{} with any by @​vishr in #​2822
• Fix typo in SetParamValues comment by @​vishr in #​2828
• Fix typo in ContextTimeout middleware comment by @​vishr in #​2827
• Improve BasicAuth middleware: use strings.Cut and RFC compliance by @​vishr in #​2825
• Fix duplicate plus operator in router backtracking logic by @​yuya-morimoto in #​2832
• Replace custom private IP range check with built-in net.IP.IsPrivate by @​kumapower17 in #​2835
• Ensure proxy connection is closed in proxyRaw function(#​2837) by @​kumapower17 in #​2838
• Update deps by @​aldas in #​2843
• Update golang.org/x/* deps by @​aldas in #​2850

v4.13.4

Compare Source

Enhancements

• chore: fix some typos in comment by @​zhuhaicity in #​2735
• CI: test with Go 1.24 by @​aldas in #​2748
• Add support for TLS WebSocket proxy by @​t-ibayashi-safie in #​2762

Security

• Update dependencies for GO-2025-3487, GO-2025-3503 and GO-2025-3595 in #​2780

---

Configuration

📅 Schedule: (in timezone Asia/Tokyo)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

ℹ️ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 12 additional dependencies were updated
• The go directive was updated for compatibility reasons

Details:

Package	Change
go	1.24.2 -> 1.25.0
github.com/stretchr/testify	v1.10.0 -> v1.11.1
github.com/labstack/gommon	v0.4.2 -> v0.5.0
github.com/mattn/go-colorable	v0.1.13 -> v0.1.14
github.com/mattn/go-isatty	v0.0.20 -> v0.0.22
golang.org/x/crypto	v0.36.0 -> v0.50.0
golang.org/x/mod	v0.24.0 -> v0.34.0
golang.org/x/net	v0.37.0 -> v0.53.0
golang.org/x/sync	v0.13.0 -> v0.20.0
golang.org/x/sys	v0.31.0 -> v0.43.0
golang.org/x/text	v0.23.0 -> v0.36.0
golang.org/x/time	v0.8.0 -> v0.15.0
golang.org/x/tools	v0.31.0 -> v0.43.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
github.com/labstack/echo/v4	v4.13.3 → v4.15.3

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Echo: Encoded slash (%2F) bypasses route-level protection and exposes static files

CVE-2026-55677 / GHSA-vfp3-v2gw-7wfq

More information

Details

Summary

Echo's router and static file handler disagree on URL path decoding. The router matches routes using the raw encoded path (preserving %2F as-is), while StaticDirectoryHandler unescapes %2F to / before resolving filesystem paths. This allows an attacker to bypass route-level access controls and read static files without authorization.

Details

Root cause 1 — router.go lines 798-802:
The router uses req.URL.RawPath for route matching when useEscapedPathForRouting is false (the default). This means /admin%2Fsecret.txt is treated as a single path segment and does NOT match the /admin/* route pattern.

if!r.useEscapedPathForRouting&&req.URL.RawPath!="" {
path=req.URL.RawPath
}

Root cause 2 — echo.go lines 559-568:
StaticDirectoryHandler calls url.PathUnescape() on the path parameter before opening files. This converts %2F back to /, resolving admin/secret.txt on disk.

if!disablePathUnescaping {
tmpPath, err:=url.PathUnescape(p)
p=tmpPath
}
name:=filepath.ToSlash(filepath.Clean(strings.TrimPrefix(p, "/")))

PoC (Screenshot)

Sample:

403:

Bypass with encoded slash:

Impact

Unauthorized static file disclosure. Applications that protect route prefixes with authentication middleware while also serving static files from a broader root are vulnerable. An attacker only needs to encode the slash (/ → %2F) in the URL to bypass all route-level protection.

Common affected pattern:

adminGroup:=e.Group("/admin", authMiddleware)
e.StaticFS("/", os.DirFS("public"))

Severity

• CVSS Score: 7.5 / 10 (High)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

References

• https://github.com/labstack/echo/security/advisories/GHSA-vfp3-v2gw-7wfq
• https://nvd.nist.gov/vuln/detail/CVE-2026-55677
• https://github.com/labstack/echo/pull/3009
• https://github.com/labstack/echo/pull/3011
• https://github.com/labstack/echo/commit/8d1ae9d3360a71672418856d58753af25f2c3986
• https://github.com/labstack/echo/commit/c3fa2a27ff92b2b8db360de614f999ef1da24725
• https://github.com/labstack/echo/releases/tag/v4.15.3
• https://github.com/labstack/echo/releases/tag/v5.2.0
• https://github.com/advisories/GHSA-vfp3-v2gw-7wfq

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

labstack/echo (github.com/labstack/echo/v4)

v4.15.3: - Static encoded-separator route bypass fix (GHSA-vfp3-v2gw-7wfq)

Compare Source

Security

• fix(static): reject encoded path separators that bypass route-level middleware by @​vishr in #​3011

Fixes GHSA-vfp3-v2gw-7wfq: an encoded path separator (%2F or %5C) in a static file URL could bypass route-level middleware (e.g. authentication on a sibling route) and disclose static files. Both StaticDirectoryHandler (used by Static/StaticFS) and the Static middleware are affected. Backport of the v5 fix (#​3009, released in v5.2.0). Thanks to @​a-tt-om and @​oran-gugu for reporting.

Full Changelog: labstack/echo@v4.15.2...v4.15.3

v4.15.2: - Context.Scheme() header validation

Compare Source

Security

• Context.Scheme() should validate values taken from header by @​aldas in #​2962

Thanks to @​shblue21 for reporting this issue.

Full Changelog: labstack/echo@v4.15.1...v4.15.2

v4.15.1

Compare Source

What's Changed

• CSRF: support older token-based CSRF protection handler that want to render token into template by @​aldas in #​2905

Full Changelog: labstack/echo@v4.15.0...v4.15.1

v4.15.0

Compare Source

Security

NB: If your application relies on cross-origin or same-site (same subdomain) requests do not blindly push this version to production

The CSRF middleware now supports the Sec-Fetch-Site header as a modern, defense-in-depth approach to CSRF
protection, implementing the OWASP-recommended Fetch Metadata API alongside the traditional token-based mechanism.

How it works:

Modern browsers automatically send the Sec-Fetch-Site header with all requests, indicating the relationship
between the request origin and the target. The middleware uses this to make security decisions:

• same-origin or none: Requests are allowed (exact origin match or direct user navigation)
• same-site: Falls back to token validation (e.g., subdomain to main domain)
• cross-site: Blocked by default with 403 error for unsafe methods (POST, PUT, DELETE, PATCH)

For browsers that don't send this header (older browsers), the middleware seamlessly falls back to
traditional token-based CSRF protection.

New Configuration Options:

• TrustedOrigins []string: Allowlist specific origins for cross-site requests (useful for OAuth callbacks, webhooks)
• AllowSecFetchSiteFunc func(echo.Context) (bool, error): Custom logic for same-site/cross-site request validation

Example:

e.Use(middleware.CSRFWithConfig(middleware.CSRFConfig{
// Allow OAuth callbacks from trusted providerTrustedOrigins: []string{"https://oauth-provider.com"},
// Custom validation for same-site requestsAllowSecFetchSiteFunc: func(c echo.Context) (bool, error) {
// Your custom authorization logic herereturnvalidateCustomAuth(c), nil// return true, err // blocks request with error// return true, nil // allows CSRF request through// return false, nil // falls back to legacy token logic
},
}))

PR: #​2858

Type-Safe Generic Parameter Binding

• Added generic functions for type-safe parameter extraction and context access by @​aldas in #​2856

  Echo now provides generic functions for extracting path, query, and form parameters with automatic type conversion,
  eliminating manual string parsing and type assertions.

  New Functions:

  • Path parameters: PathParam[T], PathParamOr[T]
  • Query parameters: QueryParam[T], QueryParamOr[T], QueryParams[T], QueryParamsOr[T]
  • Form values: FormParam[T], FormParamOr[T], FormParams[T], FormParamsOr[T]
  • Context store: ContextGet[T], ContextGetOr[T]

  Supported Types:
  Primitives (bool, string, int/uint variants, float32/float64), time.Duration, time.Time
  (with custom layouts and Unix timestamp support), and custom types implementing BindUnmarshaler,
  TextUnmarshaler, or JSONUnmarshaler.

  Example:

  // Before: Manual parsingidStr:=c.Param("id")
  id, err:=strconv.Atoi(idStr)
  // After: Type-safe with automatic parsingid, err:=echo.PathParam[int](c, "id")
  // With default valuespage, err:=echo.QueryParamOr[int](c, "page", 1)
  limit, err:=echo.QueryParamOr[int](c, "limit", 20)
  // Type-safe context access (no more panics from type assertions)user, err:=echo.ContextGet[*User](c, "user")

PR: #​2856

DEPRECATION NOTICE Timeout Middleware Deprecated - Use ContextTimeout Instead

The middleware.Timeout middleware has been deprecated due to fundamental architectural issues that cause
data races. Use middleware.ContextTimeout or middleware.ContextTimeoutWithConfig instead.

Why is this being deprecated?

The Timeout middleware manipulates response writers across goroutine boundaries, which causes data races that
cannot be reliably fixed without a complete architectural redesign. The middleware:

• Swaps the response writer using http.TimeoutHandler
• Must be the first middleware in the chain (fragile constraint)
• Can cause races with other middleware (Logger, metrics, custom middleware)
• Has been the source of multiple race condition fixes over the years

What should you use instead?

The ContextTimeout middleware (available since v4.12.0) provides timeout functionality using Go's standard
context mechanism. It is:

• Race-free by design
• Can be placed anywhere in the middleware chain
• Simpler and more maintainable
• Compatible with all other middleware

Migration Guide:

// Before (deprecated):e.Use(middleware.Timeout())
// After (recommended):e.Use(middleware.ContextTimeout(30*time.Second))

Important Behavioral Differences:

1. Handler cooperation required: With ContextTimeout, your handlers must check context.Done() for cooperative
   cancellation. The old Timeout middleware would send a 503 response regardless of handler cooperation, but had
   data race issues.

2. Error handling: ContextTimeout returns errors through the standard error handling flow. Handlers that receive
   context.DeadlineExceeded should handle it appropriately:

e.GET("/long-task", func(c echo.Context) error {
ctx:=c.Request().Context()
// Example: database query with contextresult, err:=db.QueryContext(ctx, "SELECT * FROM large_table")
iferr!=nil {
iferrors.Is(err, context.DeadlineExceeded) {
// Handle timeoutreturnecho.NewHTTPError(http.StatusServiceUnavailable, "Request timeout")
}
returnerr
}
returnc.JSON(http.StatusOK, result)
})

3. Background tasks: For long-running background tasks, use goroutines with context:

e.GET("/async-task", func(c echo.Context) error {
ctx:=c.Request().Context()
resultCh:=make(chanResult, 1)
errCh:=make(chanerror, 1)
gofunc() {
result, err:=performLongTask(ctx)
iferr!=nil {
errCh<-errreturn
}
resultCh<-result
}()
select {
caseresult:=<-resultCh:
returnc.JSON(http.StatusOK, result)
caseerr:=<-errCh:
returnerrcase<-ctx.Done():
returnecho.NewHTTPError(http.StatusServiceUnavailable, "Request timeout")
}
})

Enhancements

• Fixes by @​aldas in #​2852
• Generic functions by @​aldas in #​2856
• CRSF with Sec-Fetch-Site checks by @​aldas in #​2858

v4.14.0

Compare Source

middleware.Logger has been deprecated. For request logging, use middleware.RequestLogger or
middleware.RequestLoggerWithConfig.

middleware.RequestLogger replaces middleware.Logger, offering comparable configuration while relying on the
Go standard library’s new slog logger.

The previous default output format was JSON. The new default follows the standard slog logger settings.
To continue emitting request logs in JSON, configure slog accordingly:

slog.SetDefault(slog.New(slog.NewJSONHandler(os.Stdout, nil)))
e.Use(middleware.RequestLogger())

Security

• Logger middleware json string escaping and deprecation by @​aldas in #​2849

Enhancements

• Update deps by @​aldas in #​2807
• refactor to use reflect.TypeFor by @​cuiweixie in #​2812
• Use Go 1.25 in CI by @​aldas in #​2810
• Modernize context.go by replacing interface{} with any by @​vishr in #​2822
• Fix typo in SetParamValues comment by @​vishr in #​2828
• Fix typo in ContextTimeout middleware comment by @​vishr in #​2827
• Improve BasicAuth middleware: use strings.Cut and RFC compliance by @​vishr in #​2825
• Fix duplicate plus operator in router backtracking logic by @​yuya-morimoto in #​2832
• Replace custom private IP range check with built-in net.IP.IsPrivate by @​kumapower17 in #​2835
• Ensure proxy connection is closed in proxyRaw function(#​2837) by @​kumapower17 in #​2838
• Update deps by @​aldas in #​2843
• Update golang.org/x/* deps by @​aldas in #​2850

v4.13.4

Compare Source

Enhancements

• chore: fix some typos in comment by @​zhuhaicity in #​2735
• CI: test with Go 1.24 by @​aldas in #​2748
• Add support for TLS WebSocket proxy by @​t-ibayashi-safie in #​2762

Security

• Update dependencies for GO-2025-3487, GO-2025-3503 and GO-2025-3595 in #​2780

---

Configuration

📅 Schedule: (in timezone Asia/Tokyo)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

ℹ️ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 12 additional dependencies were updated
• The go directive was updated for compatibility reasons

Details:

Package	Change
go	1.24.2 -> 1.25.0
github.com/stretchr/testify	v1.10.0 -> v1.11.1
github.com/labstack/gommon	v0.4.2 -> v0.5.0
github.com/mattn/go-colorable	v0.1.13 -> v0.1.14
github.com/mattn/go-isatty	v0.0.20 -> v0.0.22
golang.org/x/crypto	v0.36.0 -> v0.50.0
golang.org/x/mod	v0.24.0 -> v0.34.0
golang.org/x/net	v0.37.0 -> v0.53.0
golang.org/x/sync	v0.13.0 -> v0.20.0
golang.org/x/sys	v0.31.0 -> v0.43.0
golang.org/x/text	v0.23.0 -> v0.36.0
golang.org/x/time	v0.8.0 -> v0.15.0
golang.org/x/tools	v0.31.0 -> v0.43.0