Skip to content

Penetration detection stops scanning a request after a value with no reportable threat category

Moderate
rennf93 published GHSA-w9j2-2m3v-5hcc Oct 15, 2026

Package

gomod github.com/rennf93/guard-core-go/v4 (Go)

Affected versions

< 4.4.0

Patched versions

4.4.0

Description

Impact

detectThreat in guardcore/pipeline.go scans every value of a request (path, query parameters, headers, body) for penetration patterns. When the detector reported a threat for a value but none of that value's threats carried a reportable category, the scan returned a clean verdict for the whole request instead of moving on to the next value. Two cases trigger it:

  • a semantic-only threat (semantic threats carry no category), and
  • a threat whose categories are all disabled or skipped for that component (for example ssrf on the excluded proxy headers).

Every value scanned after that one, including later headers and the request body, was never checked. A request that puts such a value early can carry an attack payload in a later value without it being detected or blocked.

Patches

Fixed in v4.4.0. A value whose threats are all filtered out is no longer a threat and the scan continues with the next value; a semantic-only threat is reported (with its attack type as the category), matching the Python reference engine.

Workarounds

None that keep detection enabled. Upgrade to v4.4.0.

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

CVE ID

No known CVE

Weaknesses

Protection Mechanism Failure

The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product. Learn more on MITRE.

Credits