CVE-2020-13299

HIGHNVD 8.18.1—

8.1

A vulnerability was discovered in GitLab versions before 13.1.10, 13.2.8 and 13.3.4. The revocation feature was not revoking all session tokens and one could re-use it to obtain a valid session.

CVSS v3: 8.1
EG Score: 8.1(medium)
EPSS: 40.2%
KEV: Not listed

Published

September 14, 2020

Last Modified

November 21, 2024

References (6)

cve@gitlabhttps://gitlab.com/gitlab-org/cves/-/blob/master/2020/CVE-2020-13299.json
cve@gitlabhttps://gitlab.com/gitlab-org/gitlab/-/issues/222508
cve@gitlabhttps://hackerone.com/reports/896225
af854a3a-2127-422b-91ae-364da2661108https://gitlab.com/gitlab-org/cves/-/blob/master/2020/CVE-2020-13299.json
af854a3a-2127-422b-91ae-364da2661108https://gitlab.com/gitlab-org/gitlab/-/issues/222508
af854a3a-2127-422b-91ae-364da2661108https://hackerone.com/reports/896225

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-613Insufficient Session Expiration

Data Freshness Timeline

(refreshed 11× in last 7d / 18× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-29 13:42 UTCepss_batch
2026-05-29 13:42 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-27 13:39 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-23 07:51 UTCEG score recompute
2026-05-23 07:51 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2020-13299?

CVE-2020-13299 is a high vulnerability published on September 14, 2020. A vulnerability was discovered in GitLab versions before 13.1.10, 13.2.8 and 13.3.4. The revocation feature was not revoking all session tokens and one could re-use it to obtain a valid session.

When was CVE-2020-13299 disclosed?

CVE-2020-13299 was first published in the National Vulnerability Database on September 14, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2020-13299 actively exploited?

CVE-2020-13299 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 40.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2020-13299?

CVE-2020-13299 has a CVSS v3 base score of 8.1 (NVD).

How do I remediate CVE-2020-13299?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-13299, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-13299

Explore →

Is Your Infrastructure Affected by CVE-2020-13299?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2020-13299

📅 Published

🔄 Last Modified

🔗 References (6)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2020-13299?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (6)

Frequently asked(5)

Related CVEs(same CWE)