CVE-2018-20744: The Olivier Poitrey Go CORS handler through 1.3.0 actively converts a wildcard CORS policy into reflecting an

Q: How do I fix CVE-2018-20744?

go cors: upgrade to newer than 1.3.0. Exact commands for each OS are on this page.

Q: Is CVE-2018-20744 being exploited?

CVE-2018-20744 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2018-20744 affect?

CVE-2018-20744 affects go cors. Severity is medium (CVSS 5.9). The Olivier Poitrey Go CORS handler through 1.3.0 actively converts a wildcard CORS policy into reflecting an arbitrary Origin header value, which is incompatible with the CORS security design, and could lead to CORS misconfiguration securi

Q: How urgent is CVE-2018-20744?

Priority 39/100. Remotely exploitable, no login, no user action

Routine

MEDIUM 5.9REMOTEUPGRADE

CVE-2018-20744 is a medium-severity flaw (CVSS 5.9) affecting go cors. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Olivier Poitrey Go CORS handler through 1.3.0 actively converts a wildcard CORS policy into reflecting an arbitrary Origin header value, which is incompatible with the CORS security design, and could lead to CORS misconfiguration security problems.

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.9 (Medium)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.7% (top 46%)
CISA exploited list	No
Weakness	CWE-346
Published	2019-01-28
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: go cors project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2019-01-28 08:29 UTCPublished CVE record published
2026-06-17 01:53 UTCUpdated Record last modified

go cors project go cors UPGRADE

Affected: <= 1.3.0

Fixed in: newer than 1.3.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy go-cors || rpm -q go-cors || go-cors --version

2. UPGRADE to newer than 1.3.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade go-cors

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade go-cors

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2018-20744?

go cors: upgrade to newer than 1.3.0. Exact commands for each OS are on this page.

Is CVE-2018-20744 being exploited?

CVE-2018-20744 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2018-20744 affect?

CVE-2018-20744 affects go cors. Severity is medium (CVSS 5.9). The Olivier Poitrey Go CORS handler through 1.3.0 actively converts a wildcard CORS policy into reflecting an arbitrary Origin header value, which is incompatible with the CORS security design, and could lead to CORS misconfiguration securi

How urgent is CVE-2018-20744?

Priority 39/100. Remotely exploitable, no login, no user action

References

← Back to latest CVEs