Our engineers set up and run your first AI security scan. Get in touch

LLM09: Misinformation

Hallucinated, biased, or stale model responses presented as authoritative output.

Last reviewed September 2026

Why LLM09 evidence is hard

In OWASP LLM Top 10, Misinformation addresses reliability. Hallucinated, biased, or stale model responses presented as authoritative output. Penaxtra records this control at medium severity and establishes its state by exercising it against the running system, so the result reflects observed behavior rather than a documented assertion.

How Penaxtra maps to LLM09

Penaxtra ships adversarial probe families that target misinformation directly. Each probe runs against the live endpoint on a schedule, and every triggering response is scored by deterministic checks that run inside our own infrastructure before it is recorded as a finding under the LLM09 identifier. The OWASP LLM Top 10 LLM09 identifier is attached when the finding is created, so it appears in the exported evidence pack already mapped to the control. Where the same weakness maps to another framework, the finding carries those control identifiers as well.

LLM09 capabilities

Probe and check coverage aligned to LLM09 (Misinformation)

Findings tagged with the OWASP LLM Top 10 LLM09 identifier

Penaxtra severity for this control (medium)

Cross-framework identifiers attached to the same finding where controls overlap

PDF and JSON evidence export with the control identifier attached

LLM09 control coverage

Findings for LLM09 carry the OWASP LLM Top 10 LLM09 identifier along with the corresponding control identifiers in the other frameworks Penaxtra maps, so one result is reflected across each mapped framework.

Frequently asked

What is LLM09 (Misinformation)?

Hallucinated, biased, or stale model responses presented as authoritative output. It is an OWASP LLM Top 10 control; Penaxtra assesses it at medium severity.

How does Penaxtra test for LLM09?

Penaxtra ships adversarial probe families that target misinformation directly. Each probe runs against the live endpoint on a schedule, and every triggering response is scored by deterministic checks that run inside our own infrastructure before it is recorded as a finding under the LLM09 identifier.

Does a finding for LLM09 help with an audit?

Each finding is tagged with the OWASP LLM Top 10 LLM09 identifier and exported in the PDF and JSON evidence pack, so it appears on the auditor control list with the identifier already attached.