Security advisory
Pterodactyl is an open-source game server management panel built with PHP 7, React, and Go. A malicious user can modify the contents of a `confirmation_token` input during the two-factor authentication process to reference a cache value not associated with the login attempt. In rare cases this can allow a malicious actor to authenticate as a random user in the Panel. The malicious user must target an account with two-factor authentication enabled, and then must provide a correct two-factor authentication token before being authenticated as that user. Due to a validation flaw in the logic handling user authentication during the two-factor authentication process a malicious user can trick the system into loading credentials for an arbitrary user by modifying the token sent to the server. This authentication flaw is present in the `LoginCheckpointController@__invoke` method which handles two-factor authentication for a user. This controller looks for a request input parameter called `confirmation_token` which is expected to be a 64 character random alpha-numeric string that references a value within the Panel's cache containing a `user_id` value. This value is then used to fetch the user that attempted to login, and lookup their two-factor authentication token. Due to the design of this system, any element in the cache that contains only digits could be referenced by a malicious user, and whatever value is stored at that position would be used as the `user_id`. There are a few d
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2021-41129
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 31 Oct 2026, 11:20 UTC · Revision 1
Source evidence
Pterodactyl is an open-source game server management panel built with PHP 7, React, and Go. A malicious user can modify the contents of a `confirmation_token` input during the two-factor authentication process to reference a cache value not associated with the login attempt. In rare cases this can allow a malicious actor to authenticate as a random user in the Panel. The malicious user must target an account with two-factor authentication enabled, and then must provide a correct two-factor authentication token before being authenticated as that user. Due to a validation flaw in the logic handling user authentication during the two-factor authentication process a malicious user can trick the system into loading credentials for an arbitrary user by modifying the token sent to the server. This authentication flaw is present in the `LoginCheckpointController@__invoke` method which handles two-factor authentication for a user. This controller looks for a request input parameter called `confirmation_token` which is expected to be a 64 character random alpha-numeric string that references a value within the Panel's cache containing a `user_id` value. This value is then used to fetch the user that attempted to login, and lookup their two-factor authentication token. Due to the design of this system, any element in the cache that contains only digits could be referenced by a malicious user, and whatever value is stored at that position would be used as the `user_id`. There are a few d
osv:CVE-2021-41129
Complete source record
{
"id": "c91c73fe085f49229792790183281ad23af6fb6b12b01e9590697c7ac7529941",
"url": "https://osv.dev/vulnerability/CVE-2021-41129",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "CVE-2021-41129",
"summary": "Pterodactyl is an open-source game server management panel built with PHP 7, React, and Go. A malicious user can modify the contents of a `confirmation_token` input during the two-factor authentication process to reference a cache value not associated with the login attempt. In rare cases this can allow a malicious actor to authenticate as a random user in the Panel. The malicious user must target an account with two-factor authentication enabled, and then must provide a correct two-factor authentication token before being authenticated as that user. Due to a validation flaw in the logic handling user authentication during the two-factor authentication process a malicious user can trick the system into loading credentials for an arbitrary user by modifying the token sent to the server. This authentication flaw is present in the `LoginCheckpointController@__invoke` method which handles two-factor authentication for a user. This controller looks for a request input parameter called `confirmation_token` which is expected to be a 64 character random alpha-numeric string that references a value within the Panel's cache containing a `user_id` value. This value is then used to fetch the user that attempted to login, and lookup their two-factor authentication token. Due to the design of this system, any element in the cache that contains only digits could be referenced by a malicious user, and whatever value is stored at that position would be used as the `user_id`. There are a few d",
"evidence": "osv:CVE-2021-41129",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2021-41129",
"aliases": [
"CVE-2021-41129",
"GHSA-5vfx-8w6m-h3v4"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/pterodactyl/panel",
"type": "GIT",
"events": [
{
"introduced": "d795668fc202707749bb418e1a735338f78d26dd"
},
{
"fixed": "c57eb2c9e6e31823669c4ec444afed9f3e156a5e"
},
{
"fixed": "4a84c36009be10dbd83051ac1771662c056e4977"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:pterodactyl:panel:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "1.0.0"
},
{
"fixed": "1.6.2"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "4a84c36009be10dbd83051ac1771662c056e4977"
}
],
"source": "REFERENCES_COMMIT"
},
{
"range": [
{
"fixed": "c57eb2c9e6e31823669c4ec444afed9f3e156a5e"
}
],
"source": "REFERENCES_TAG",
"original_tag": "v1.6.2"
}
]
}
}
],
"versions": [
"v1.6.1",
"v1.6.0",
"v1.5.1",
"v1.5.0",
"v1.4.2",
"v1.4.1",
"v1.4.0",
"v1.3.2",
"v1.3.1",
"v1.3.0",
"v1.2.2",
"v1.2.1",
"v1.2.0",
"v1.1.3",
"v1.1.2",
"v1.1.1",
"v1.1.0",
"v1.0.3",
"v1.0.2",
"v1.0.1",
"v1.0.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2021-41129.json"
}
}
],
"modified": "2026-10-20T10:53:56.091226929Z",
"provider": "osv",
"references": [
"https://github.com/pterodactyl/panel/blob/v1.6.2/CHANGELOG.md#v162",
"https://github.com/pterodactyl/panel/releases/tag/v1.6.2",
"https://github.com/pterodactyl/panel/security/advisories/GHSA-5vfx-8w6m-h3v4",
"https://github.com/pterodactyl/panel/commit/4a84c36009be10dbd83051ac1771662c056e4977"
],
"provider_metadata": {}
},
"related_cves": [
{
"value": "CVE-2021-41129",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 384774,
"published_at": "2021-10-06T20:15:19.897+00:00"
}