URL scheme validation throws a generic Error instead of a project-specific error class (such as ActionableError). In highly specific framework environments, generic exceptions might not be properly handled, routed, or surfaced to the client, which can cause security validation failures to be silently suppressed or incorrectly processed.
Explore
Rule Explorer
Search the public rule index by CVE, GHSA, CWE, language, framework, author, or rule slug. Filter by language, framework, severity, confidence, license, and validation status.
- Public rules
- 4797
- Downloads
- 7.4M
- Verified
- 4797
- Authors
- 2
Search the rule indexUse CVE, GHSA, CWE, language, framework, package, or rule slug.
CVE-2026-35394: Improper Error Class In Url Validationcve-2026-35394-improper-error-class-in-url-validation
CVE-2025-25204: Go Nil Error Return On Empty Checkcve-2025-25204-go-nil-error-return-on-empty-check
Returning an unassigned `err` variable inside an empty collection or nil check (`len(x) == 0` or `x == nil`) often results in inadvertently returning `nil` when a failure was intended. Ensure that you explicitly create and return a new error using `fmt.Errorf` or `errors.New` if this logic path represents a failure state.
All matching rules loaded.