Skip to content
Fencer Vulns
medium 4.3

CVE-2020-27831 json

A flaw was found in Red Hat Quay, where it does not properly protect the authorization token when authorizing email addresses for repositor…

published 2021-05-26 5 y ago modified 2026-06-17 4 mo ago also EUVD-2020-20330

cvss
4.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 46%
public exploits
0
none known

Summary

A flaw was found in Red Hat Quay, where it does not properly protect the authorization token when authorizing email addresses for repository email notifications. This flaw allows an attacker to add email addresses they do not own to repository notifications.

Patch / fix

  • redhat quay 3.3.3

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-27831 updated cvss 2.6

quay: email notifications authorization bypass

  • Red Hat Quay v3 quay/quay-rhel8-operator v3.3.3-3, quay/quay-operator-bundle v3.3.3-3, quay/quay-openshift-bridge-rhel8-operator v3.3.3-1, quay/quay-container-security-rhel8-operator v3.3.3-2, quay/quay-openshift-bridge-rhel8-operator-metadata v3.3.2-2, quay/quay-container-security-rhel8-operator-metadata v3.3.3-4
    fixed: vendor fix “Disable email using the configuration app.” RHSA-2021:0050

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.55% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:N/I:P/A:N

Affected products

  • n/a quay

Classification

Weakness
  • CWE-284 Improper Access Control
  • CWE-522 Insufficiently Protected Credentials

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.