{"items":[{"id":"NVI-00005371","kind":"vulnerability","title":"Pterodactyl has a database resource limit bypass via race condition in Client API","revision":5,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-fgmm-w5cx-vrfw","CVE-2026-35202"],"plain_summary":"GitHub lists this reviewed advisory for pterodactyl/panel. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-25e198bf1f304b68835b51c71bf57311"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 1.12.3 for pterodactyl/panel. Confirm the publisher’s latest guidance.","source_ids":["sr-8cb14504666da32ca23647d7820e3b68"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-07-22T19:10:00.120Z","value":"2.3 LOW (4.0)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-0f24bee735467f75ec7902164b08e086"},{"kind":"EPSS","as_of":"2026-11-01T12:00:16.000Z","value":"0.212%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.11516. Missing scores are unknown.","source_id":"sr-25e198bf1f304b68835b51c71bf57311"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-6054ea90c3d80a2636f194551c38b237","url":"https://github.com/advisories/GHSA-fgmm-w5cx-vrfw","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-fgmm-w5cx-vrfw","publisher":"GitHub Advisory Database","observed_at":"2026-11-06T20:56:39.448Z"},{"id":"sr-8cb14504666da32ca23647d7820e3b68","url":"https://github.com/advisories/GHSA-fgmm-w5cx-vrfw","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-fgmm-w5cx-vrfw","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:20.404Z"},{"id":"sr-0f24bee735467f75ec7902164b08e086","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-35202","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-35202","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:23:23.484Z"},{"id":"sr-25e198bf1f304b68835b51c71bf57311","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-35202","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:28:32.277Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-6054ea90c3d80a2636f194551c38b237"],"technology":"pterodactyl/panel","known_exclusions":[],"conditions_summary":"### Summary\n\nThe Pterodactyl Client API has a logic flaw that lets users bypass their assigned limits for database allocations. This happens because the database locking mechanism used in the controllers is totally broken and doesn't actually lock anything.\n\n### Details\n\nInside `DatabaseController.php`, the code tries to prevent multiple databases from being created at once by calling `$server->databases()->lockForUpdate()`. In Laravel, this just configures a query builder but never actually sends a command to the database because it’s missing a terminal method like `count()` or `get()`. It’s basically a no-op that does nothing.\n\nSince there’s no real lock, multiple requests hitting the endpoint at the exact same time will all see that the database count is under the limit. They all move forward to the `DeployServerDatabaseService` and successfully create extra resources on the physical host.\n\n### Impact\n\nUsers are able to create more databases than they are supposed to, potentially also breaking the web interface.","public_affected_ranges":["< 1.12.3"]},{"certainty":"source_listed","source_ids":["sr-8cb14504666da32ca23647d7820e3b68"],"technology":"pterodactyl/panel","known_exclusions":[],"conditions_summary":"### Summary\n\nThe Pterodactyl Client API has a logic flaw that lets users bypass their assigned limits for database allocations. This happens because the database locking mechanism used in the controllers is totally broken and doesn't actually lock anything.\n\n### Details\n\nInside `DatabaseController.php`, the code tries to prevent multiple databases from being created at once by calling `$server->databases()->lockForUpdate()`. In Laravel, this just configures a query builder but never actually sends a command to the database because it’s missing a terminal method like `count()` or `get()`. It’s basically a no-op that does nothing.\n\nSince there’s no real lock, multiple requests hitting the endpoint at the exact same time will all see that the database count is under the limit. They all move forward to the `DeployServerDatabaseService` and successfully create extra resources on the physical host.\n\n### Impact\n\nUsers are able to create more databases than they are supposed to, potentially also breaking the web interface.","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 1.12.3"]}],"null_published_at":"2026-11-08T15:11:47.504Z","source_updated_at":"2026-06-09T11:00:10.000Z","source_disclosed_at":"2026-05-26T19:30:02.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:42:20.404Z"},{"id":"NVI-00005371","kind":"vulnerability","title":"Pterodactyl has a database resource limit bypass via race condition in Client API","revision":4,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-fgmm-w5cx-vrfw","CVE-2026-35202"],"plain_summary":"OSV carries this publisher advisory for pterodactyl/panel. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 1.12.3 for pterodactyl/panel. Confirm the publisher’s latest guidance.","source_ids":["sr-8cb14504666da32ca23647d7820e3b68"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-25e198bf1f304b68835b51c71bf57311"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-07-22T19:10:00.120Z","value":"2.3 LOW (4.0)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-0f24bee735467f75ec7902164b08e086"},{"kind":"EPSS","as_of":"2026-11-01T12:00:16.000Z","value":"0.212%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.11516. Missing scores are unknown.","source_id":"sr-25e198bf1f304b68835b51c71bf57311"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-8cb14504666da32ca23647d7820e3b68","url":"https://github.com/advisories/GHSA-fgmm-w5cx-vrfw","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-fgmm-w5cx-vrfw","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:20.404Z"},{"id":"sr-0f24bee735467f75ec7902164b08e086","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-35202","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-35202","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:23:23.484Z"},{"id":"sr-25e198bf1f304b68835b51c71bf57311","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-35202","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:28:32.277Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-8cb14504666da32ca23647d7820e3b68"],"technology":"pterodactyl/panel","known_exclusions":[],"conditions_summary":"### Summary\n\nThe Pterodactyl Client API has a logic flaw that lets users bypass their assigned limits for database allocations. This happens because the database locking mechanism used in the controllers is totally broken and doesn't actually lock anything.\n\n### Details\n\nInside `DatabaseController.php`, the code tries to prevent multiple databases from being created at once by calling `$server->databases()->lockForUpdate()`. In Laravel, this just configures a query builder but never actually sends a command to the database because it’s missing a terminal method like `count()` or `get()`. It’s basically a no-op that does nothing.\n\nSince there’s no real lock, multiple requests hitting the endpoint at the exact same time will all see that the database count is under the limit. They all move forward to the `DeployServerDatabaseService` and successfully create extra resources on the physical host.\n\n### Impact\n\nUsers are able to create more databases than they are supposed to, potentially also breaking the web interface.","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 1.12.3"]}],"null_published_at":"2026-11-06T15:18:11.419Z","source_updated_at":"2026-09-10T03:50:46.734Z","source_disclosed_at":"2026-05-26T19:30:02.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:42:20.404Z"},{"id":"NVI-00005371","kind":"vulnerability","title":"Pterodactyl has a database resource limit bypass via race condition in Client API","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-fgmm-w5cx-vrfw","CVE-2026-35202"],"plain_summary":"OSV carries this publisher advisory for pterodactyl/panel. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 1.12.3 for pterodactyl/panel. Confirm the publisher’s latest guidance.","source_ids":["sr-8cb14504666da32ca23647d7820e3b68"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-9d368e9eca7ed599a452ea166f4bd9ec"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-07-22T19:10:00.120Z","value":"2.3 LOW (4.0)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-0f24bee735467f75ec7902164b08e086"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.212%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.11521. Missing scores are unknown.","source_id":"sr-9d368e9eca7ed599a452ea166f4bd9ec"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-8cb14504666da32ca23647d7820e3b68","url":"https://github.com/advisories/GHSA-fgmm-w5cx-vrfw","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-fgmm-w5cx-vrfw","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:20.404Z"},{"id":"sr-0f24bee735467f75ec7902164b08e086","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-35202","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-35202","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:23:23.484Z"},{"id":"sr-9d368e9eca7ed599a452ea166f4bd9ec","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-35202","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.377Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-8cb14504666da32ca23647d7820e3b68"],"technology":"pterodactyl/panel","known_exclusions":[],"conditions_summary":"### Summary\n\nThe Pterodactyl Client API has a logic flaw that lets users bypass their assigned limits for database allocations. This happens because the database locking mechanism used in the controllers is totally broken and doesn't actually lock anything.\n\n### Details\n\nInside `DatabaseController.php`, the code tries to prevent multiple databases from being created at once by calling `$server->databases()->lockForUpdate()`. In Laravel, this just configures a query builder but never actually sends a command to the database because it’s missing a terminal method like `count()` or `get()`. It’s basically a no-op that does nothing.\n\nSince there’s no real lock, multiple requests hitting the endpoint at the exact same time will all see that the database count is under the limit. They all move forward to the `DeployServerDatabaseService` and successfully create extra resources on the physical host.\n\n### Impact\n\nUsers are able to create more databases than they are supposed to, potentially also breaking the web interface.","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 1.12.3"]}],"null_published_at":"2026-11-04T02:53:03.171Z","source_updated_at":"2026-09-10T03:50:46.734Z","source_disclosed_at":"2026-05-26T19:30:02.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:42:20.404Z"},{"id":"NVI-00005371","kind":"vulnerability","title":"Pterodactyl has a database resource limit bypass via race condition in Client API","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-fgmm-w5cx-vrfw","CVE-2026-35202"],"plain_summary":"OSV carries this publisher advisory for pterodactyl/panel. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 1.12.3 for pterodactyl/panel. Confirm the publisher’s latest guidance.","source_ids":["sr-8cb14504666da32ca23647d7820e3b68"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-0f24bee735467f75ec7902164b08e086"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-07-22T19:10:00.120Z","value":"2.3 LOW (4.0)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-0f24bee735467f75ec7902164b08e086"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-8cb14504666da32ca23647d7820e3b68","url":"https://github.com/advisories/GHSA-fgmm-w5cx-vrfw","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-fgmm-w5cx-vrfw","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:20.404Z"},{"id":"sr-0f24bee735467f75ec7902164b08e086","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-35202","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-35202","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:23:23.484Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-8cb14504666da32ca23647d7820e3b68"],"technology":"pterodactyl/panel","known_exclusions":[],"conditions_summary":"### Summary\n\nThe Pterodactyl Client API has a logic flaw that lets users bypass their assigned limits for database allocations. This happens because the database locking mechanism used in the controllers is totally broken and doesn't actually lock anything.\n\n### Details\n\nInside `DatabaseController.php`, the code tries to prevent multiple databases from being created at once by calling `$server->databases()->lockForUpdate()`. In Laravel, this just configures a query builder but never actually sends a command to the database because it’s missing a terminal method like `count()` or `get()`. It’s basically a no-op that does nothing.\n\nSince there’s no real lock, multiple requests hitting the endpoint at the exact same time will all see that the database count is under the limit. They all move forward to the `DeployServerDatabaseService` and successfully create extra resources on the physical host.\n\n### Impact\n\nUsers are able to create more databases than they are supposed to, potentially also breaking the web interface.","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 1.12.3"]}],"null_published_at":"2026-11-01T14:34:07.521Z","source_updated_at":"2026-09-10T03:50:46.734Z","source_disclosed_at":"2026-05-26T19:30:02.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:42:20.404Z"},{"id":"NVI-00005371","kind":"vulnerability","title":"Pterodactyl has a database resource limit bypass via race condition in Client API","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-fgmm-w5cx-vrfw","CVE-2026-35202"],"plain_summary":"OSV carries this publisher advisory for pterodactyl/panel. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 1.12.3 for pterodactyl/panel. Confirm the publisher’s latest guidance.","source_ids":["sr-8cb14504666da32ca23647d7820e3b68"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-8cb14504666da32ca23647d7820e3b68","url":"https://github.com/advisories/GHSA-fgmm-w5cx-vrfw","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-fgmm-w5cx-vrfw","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:20.404Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-8cb14504666da32ca23647d7820e3b68"],"technology":"pterodactyl/panel","known_exclusions":[],"conditions_summary":"### Summary\n\nThe Pterodactyl Client API has a logic flaw that lets users bypass their assigned limits for database allocations. This happens because the database locking mechanism used in the controllers is totally broken and doesn't actually lock anything.\n\n### Details\n\nInside `DatabaseController.php`, the code tries to prevent multiple databases from being created at once by calling `$server->databases()->lockForUpdate()`. In Laravel, this just configures a query builder but never actually sends a command to the database because it’s missing a terminal method like `count()` or `get()`. It’s basically a no-op that does nothing.\n\nSince there’s no real lock, multiple requests hitting the endpoint at the exact same time will all see that the database count is under the limit. They all move forward to the `DeployServerDatabaseService` and successfully create extra resources on the physical host.\n\n### Impact\n\nUsers are able to create more databases than they are supposed to, potentially also breaking the web interface.","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 1.12.3"]}],"null_published_at":"2026-10-31T22:13:01.462Z","source_updated_at":"2026-09-10T03:50:46.734Z","source_disclosed_at":"2026-05-26T19:30:02.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:42:20.404Z"}],"next_cursor":null,"snapshot_revision":"42594"}