NVD / CVE Program· CNA Go

CVE-2020-36567: Arbitrary log line injection in github.com/gin-gonic/gin

HighCVSS 7.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 30/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 1.5% (FIRST EPSS); higher than 75.3% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
Fixed version: github.com/gin-gonic/gin github.com/gin-gonic/gin 1.6.0.

Low priority for now. Upgrade to github.com/gin-gonic/gin github.com/gin-gonic/gin 1.6.0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Unsanitized input in the default logger in github.com/gin-gonic/gin before v1.6.0 allows remote attackers to inject arbitrary log lines.

Pre-auth

Published: Dec 27, 2022
Updated: Jun 16, 2026
EPSS: 1.5% · 75th percentile
CWE: CWE-116

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 30 / 40 · 7.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 1.5%

CISA SSVC decision

Exploitation: proof of concept
Automatable: yes
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
gin-gonic	gin	cpe:2.3:a:gin-gonic:gin

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Go). Independent of NVD's CPE analysis and usually ahead of it.

github.com/gin-gonic/gin github.com/gin-gonic/gin
- before 1.6.0affected · semver

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

gin-gonic ginbefore 1.6.0

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	golang-github-gin-gonic-gin	before 1.6.3-1	1.6.3-1
Go	github.com/gin-gonic/gin	before 1.6.0	1.6.0

Same product

gin-gonic: all records

Other highest-scoring records for the same primary product.

CVE-2023-26125Versions of the package github.com/gin-gonic/gin before 1.9.0 are vulnerable to Improper Input Validation by allowing an attacker to use a…
29Monitor
CVE-2020-28483HTTP Response Splitting
28Monitor
CVE-2023-29401Improper handling of filenames in Content-Disposition HTTP header in github.com/gin-gonic/gin
17Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
github.com/gin-gonic/gin github.com/gin-gonic/gin	1.6.0	Vendor (CNA)
debian:golang-github-gin-gonic-gin	1.6.3-1 · Debian:12	Package registry (OSV)
Go:github.com/gin-gonic/gin	1.6.0	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.