CVE-2019-7628

Pagure 5.2 leaks API keys by e-mailing them to users. Few e-mail servers validate TLS certificates, so it is easy for man-in-the-middle attackers to read these e-mails and gain access to Pagure on behalf of other users. This issue is found in the API token expiration reminder cron job in files/api_key_expire_mail.py; disabling that job is also a viable solution. (E-mailing a substring of the API key was an attempted, but rejected, solution.)

Published: 2019-02-07 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2019-7628 is rated Moderate Risk (43.5/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 0.90%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2019-7628

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.17% 0.90% +0.74%
2 2025-03-17 0.12% 0.17% +0.04%
3 2023-03-07 — 0.12% —

Full EPSS history (7 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2019-7628

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.9 3.0 MEDIUM
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 2.2 3.6 [email protected]
4.3 2.0 MEDIUM
AV:N/AC:M/Au:N/C:P/I:N/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:N)
No availability impact.
 8.6 2.9 [email protected]

Weakness enumeration for CVE-2019-7628

OS Trackers for CVE-2019-7628

vendor priority summary link
debian unimportant CVE-2019-7628 unimportant priority: Debian including 1 source packages (pagure), 3 status rows across 3 suites (bullseye, sid, trixie): resolved 3. https://security-tracker.debian.org/tracker/CVE-2019-7628

Affected software / configurations for CVE-2019-7628

Vendor Product Version Raw CPE
redhat pagure 5.2 cpe:2.3:a:redhat:pagure:5.2:*:*:*:*:*:*:*

References for CVE-2019-7628

URL Tags
https://pagure.io/pagure/c/9905fb1e64341822366b6ab1d414d2baa230af0a Issue Tracking Patch Vendor Advisory
https://pagure.io/pagure/issue/4230 Issue Tracking Patch Vendor Advisory
https://pagure.io/pagure/issue/4252 Broken Link
https://pagure.io/pagure/issue/4253 Broken Link
https://pagure.io/pagure/pull-request/4254 Issue Tracking Patch Vendor Advisory
cvelogic Threat Intelligence