Source detection
HTTP parameters, headers, cookies, file uploads, environment variables, CLI args, and framework-specific request objects.
Cognium traces tainted data across functions, files, collections, framework calls, and sanitizers. It is deterministic, reproducible, and built for codebases that change fast.
Traditional scanners match dangerous text. Cognium builds a flow graph, follows values through the program, and only reports when tainted input reaches a sensitive sink without a sanitizer.
HTTP parameters, headers, cookies, file uploads, environment variables, CLI args, and framework-specific request objects.
Flows are followed across function calls, return values, object fields, map keys, array indexes, conditionals, and common framework abstractions.
Prepared statements, HTML escaping, URL validation, framework encoders, and custom YAML definitions reduce noise without hiding risk.
The open-source engine runs without an LLM. Optional model-assisted discovery can be layered on top for deeper research workflows, while the static engine remains deterministic.
Cognium + Claude Opus 78.3% 94 / 120 CVEs Cognium static only 42.5% 51 / 120 CVEs CodeQL 22.5% 27 / 120 CVEs LLM discovery mode reads source code from scratch. Verification mode confirms exploitability. Static mode remains independent and deterministic.
Cognium ships with source, sink, and sanitizer definitions for popular server frameworks, plus YAML configuration for teams adding their own architecture patterns.
SQL injection, command injection, XSS, path traversal, SSRF, deserialization, XXE, LDAP injection, NoSQL injection, response splitting, weak randomness, weak crypto, and more.
Use Cognium locally, in pre-commit hooks, or inside CI. SARIF output plugs into GitHub code scanning and existing review workflows.
$ npm install -g cognium
$ cognium scan ./src --format sarif -o results.sarif
src/controllers/AuthController.java
[critical] sql_injection CWE-89
tainted data flows from line 12 to line 45
fix: use PreparedStatement with parameters
Found 1 vulnerability in 1 file.
Use Dev Central to find the right implementation guide, then bring design questions, framework requests, and benchmark notes into the community forums.
Start from install paths, CI examples, framework configuration, benchmark reproduction, and contribution checklists.
Open Dev CentralRoute support questions, rule ideas, integrations, and research discussions to the right open community channel.
Open ForumsContribute framework definitions, benchmark cases, editor integrations, CI examples, and research notes. The engine is MIT licensed and built in the open.