Skip to main content

Vulnerability status

Vulnerability status is shown in the vulnerabilities grid and can be any of the statuses shown in this table. You can edit the vulnerability status.


When to set this status


This is the default status of a vulnerability after it is discovered by Contrast. The vulnerability in this application could possibly be exploited.


Confirm that the vulnerability is a true finding by reviewing the source code or exploiting it.


The vulnerability appears to be a true finding based on the details provided, but requires more investigation to determine its validity.

Not a problem

The vulnerability is being accounted for without any source code changes. To set this status, you must select one of these reasons. Vulnerabilities set to this status will not revert back to Reported if found again.

  • Attack is defended by an external security control: There is another component in the environment, such as a WAF, which will prevent this vulnerability from being exploited.

  • False positive: This vulnerability was reported incorrectly. Contact Support to figure out why Contrast flagged this trace as a vulnerability.

  • Goes through an internal security control: There is custom, corrective code inside the application that will prevent this vulnerability from being exploited.

  • URL is only accessible by trusted power users: This vulnerability may only exist in specific environments, such as test, and may not exist in production environments.

  • Other: Select this option if there is another reason that no source code changes are required in order to fix this vulnerability. It is possible to replace Other with a custom value that explains why the vulnerability is Not a problem.


The vulnerability has been fixed by changing source code or config files within the application.


The vulnerability has been fixed by changing the source code or because of a reason given under the Not a problem status. A vulnerability set to this status will not revert back to Reported if found again. (This option is only available to administrators.)


This status can only be automatically set. (It can't be manually set by a user.) If a vulnerability is not reported within the time limit set in the vulnerability policy, it will automatically be set to Remediated-auto-verified.

Policies that are set to Reported, Confirmed, Suspicious are considered to be open. Policies that are set to Not a problem, Remediated, Fixed, or Remediated-Auto-verified are considered to be closed. You can filter vulnerabilities by Open to see only open statuses, or by All to see both open and closed statuses.


If the agent reports a vulnerability and Contrast has never seen it before, Contrast creates a new entry for the vulnerability. If that vulnerability already exists, Contrast updates the existing entry, issue count and number of days since it was last detected. All vulnerabilities will be reopened with the same pre-existing status, except those that were previously set to Remediated or Remediated-Auto-verified. Those will be reopened as Reported.