Inspectopedia 2026.3 Help

Taint analysis

This inspection is designed to identify potentially vulnerable sections of code where data obtained from potentially unreliable sources may be used in operations that pose security risks.

Data Flow Tracking:

The inspection tracks the flow of data from the source to its usage in critical operations. This includes analyzing the transfer of data through methods, objects, and variables.

Consider an example where user input is directly used in an SQL query without proper preprocessing. The inspection would issue a warning about a potential SQL injection.

String userInput = getUserInput(); String sqlQuery = "SELECT * FROM users WHERE username = '" + userInput + "'";

Locating this inspection

By ID

Can be used to locate inspection in e.g. Qodana configuration files, where you can quickly enable or disable it, or adjust its settings.

JvmTaintAnalysis
Via Settings dialog

Path to the inspection settings via IntelliJ Platform IDE Settings dialog, when you need to adjust inspection settings directly from your IDE.

Settings or Preferences | Editor | Inspections | Security

Inspection ID: JvmTaintAnalysis

Inspection options

Here you can find the description of settings available for the Taint analysis inspection, and the reference of their default values.

Common

Default value:

None
In-Editor Analysis

Default value:

None
Batch Analysis

Default value:

None
Trace

Default value:

None

Suppressing Inspection

You can suppress this inspection by placing the following comment marker before the code fragment where you no longer want messages from this inspection to appear:

//noinspection JvmTaintAnalysis

More detailed instructions as well as other ways and options that you have can be found in the product documentation:

Inspection Details

By default bundled with:

IntelliJ IDEA 2026.3, Qodana for JVM 2026.3,

Last modified: 20 November 2026