Fix Guidance

Every confirmed finding includes remediation guidance to help you fix the vulnerability quickly and correctly.

What's included

Explanation

A plain-language description of the vulnerability, why it's dangerous, and what the correct fix approach looks like. Written for the developer who will be making the change.

Suggested fix

When possible, Secbez generates a specific code change (patch) that addresses the vulnerability. This patch:

• Targets only the vulnerable code — no unrelated changes
• Is verified for correct syntax and formatting
• Serves as a starting point, not a blind apply-and-merge

Always review suggested fixes before applying them. Secbez understands patterns, but your team knows the full business context.

Applying fixes

1. Read the explanation to understand the root cause
2. Review the suggested fix if one is provided
3. Apply the fix (or write your own based on the guidance)
4. Open a PR — Secbez will re-scan and verify the fix resolves the finding
5. If the vulnerable code is gone or properly mitigated, the finding transitions to fixed