{"items":[{"id":"NVI-00006280","kind":"vulnerability","title":"Pixelfed doesn't check OAuth Scopes in API routes, giving elevated permissions","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-gccq-h3xj-jgvf","CVE-2024-25108"],"plain_summary":"OSV carries this publisher advisory for pixelfed/pixelfed. 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 0.11.11 for pixelfed/pixelfed. Confirm the publisher’s latest guidance.","source_ids":["sr-ae568fe947e2834182148d3e85dfe8d9"],"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-773cdb946f5f7760b5ebfda42b3173af"],"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-06-17T07:15:31.323Z","value":"9.9 CRITICAL (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-7cfcf07539c9028382926eb2e4351eb1"},{"kind":"CVSS","as_of":"2026-06-17T07:15:31.323Z","value":"8.8 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-7cfcf07539c9028382926eb2e4351eb1"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.678%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.52334. Missing scores are unknown.","source_id":"sr-773cdb946f5f7760b5ebfda42b3173af"}],"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-ae568fe947e2834182148d3e85dfe8d9","url":"https://github.com/advisories/GHSA-gccq-h3xj-jgvf","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-gccq-h3xj-jgvf","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:20.415Z"},{"id":"sr-7cfcf07539c9028382926eb2e4351eb1","url":"https://nvd.nist.gov/vuln/detail/CVE-2024-25108","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2024-25108","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T00:59:14.650Z"},{"id":"sr-773cdb946f5f7760b5ebfda42b3173af","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-2024-25108","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:03.704Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-ae568fe947e2834182148d3e85dfe8d9"],"technology":"pixelfed/pixelfed","known_exclusions":[],"conditions_summary":"### Summary\n\nWhen processing requests authorization was improperly and insufficiently checked, allowing attackers to access far more functionality than users intended, including to the administrative and moderator functionality of the Pixelfed server.\n\nThis vulnerability affects every version of Pixelfed between `v0.10.4` and `v0.11.9`, inclusive. A proof of concept of this vulnerability exists.\n\n### Details\n\nIn vulnerable versions of Pixelfed (versions before 0.11.11), when the API checked the request for permissions to perform a certain behavior, it did not check that the OAuth Application/Client had granted access to those API endpoints, it only checked if the user was authenticated via an access token, and if the user was the owner of the resource or an admin on the instance.\n\nThis meant that an attacker could request an access token for \"read\" permissions to authenticate you with their application, but the access token that they obtained actually could be used for \"write\" or even administrative actions, and the user who granted access to their account had zero knowledge of this elevated access.\n\n#### Proof of Concept\n\n1. Create an access token either via [2-legged OAuth flow](","public_affected_ranges":["ECOSYSTEM: introduced 0.10.4; fixed 0.11.11"]}],"null_published_at":"2026-11-03T17:49:21.346Z","source_updated_at":"2026-09-10T03:50:05.560Z","source_disclosed_at":"2024-02-12T15:17:23.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.415Z"},{"id":"NVI-00006280","kind":"vulnerability","title":"Pixelfed doesn't check OAuth Scopes in API routes, giving elevated permissions","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-gccq-h3xj-jgvf","CVE-2024-25108"],"plain_summary":"OSV carries this publisher advisory for pixelfed/pixelfed. 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 0.11.11 for pixelfed/pixelfed. Confirm the publisher’s latest guidance.","source_ids":["sr-ae568fe947e2834182148d3e85dfe8d9"],"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-773cdb946f5f7760b5ebfda42b3173af"],"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":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.678%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.52334. Missing scores are unknown.","source_id":"sr-773cdb946f5f7760b5ebfda42b3173af"}],"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-ae568fe947e2834182148d3e85dfe8d9","url":"https://github.com/advisories/GHSA-gccq-h3xj-jgvf","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-gccq-h3xj-jgvf","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:20.415Z"},{"id":"sr-773cdb946f5f7760b5ebfda42b3173af","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-2024-25108","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:03.704Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-ae568fe947e2834182148d3e85dfe8d9"],"technology":"pixelfed/pixelfed","known_exclusions":[],"conditions_summary":"### Summary\n\nWhen processing requests authorization was improperly and insufficiently checked, allowing attackers to access far more functionality than users intended, including to the administrative and moderator functionality of the Pixelfed server.\n\nThis vulnerability affects every version of Pixelfed between `v0.10.4` and `v0.11.9`, inclusive. A proof of concept of this vulnerability exists.\n\n### Details\n\nIn vulnerable versions of Pixelfed (versions before 0.11.11), when the API checked the request for permissions to perform a certain behavior, it did not check that the OAuth Application/Client had granted access to those API endpoints, it only checked if the user was authenticated via an access token, and if the user was the owner of the resource or an admin on the instance.\n\nThis meant that an attacker could request an access token for \"read\" permissions to authenticate you with their application, but the access token that they obtained actually could be used for \"write\" or even administrative actions, and the user who granted access to their account had zero knowledge of this elevated access.\n\n#### Proof of Concept\n\n1. Create an access token either via [2-legged OAuth flow](","public_affected_ranges":["ECOSYSTEM: introduced 0.10.4; fixed 0.11.11"]}],"null_published_at":"2026-11-01T19:14:01.605Z","source_updated_at":"2026-09-10T03:50:05.560Z","source_disclosed_at":"2024-02-12T15:17:23.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.415Z"},{"id":"NVI-00006280","kind":"vulnerability","title":"Pixelfed doesn't check OAuth Scopes in API routes, giving elevated permissions","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-gccq-h3xj-jgvf","CVE-2024-25108"],"plain_summary":"OSV carries this publisher advisory for pixelfed/pixelfed. 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 0.11.11 for pixelfed/pixelfed. Confirm the publisher’s latest guidance.","source_ids":["sr-ae568fe947e2834182148d3e85dfe8d9"],"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-ae568fe947e2834182148d3e85dfe8d9","url":"https://github.com/advisories/GHSA-gccq-h3xj-jgvf","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-gccq-h3xj-jgvf","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:20.415Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-ae568fe947e2834182148d3e85dfe8d9"],"technology":"pixelfed/pixelfed","known_exclusions":[],"conditions_summary":"### Summary\n\nWhen processing requests authorization was improperly and insufficiently checked, allowing attackers to access far more functionality than users intended, including to the administrative and moderator functionality of the Pixelfed server.\n\nThis vulnerability affects every version of Pixelfed between `v0.10.4` and `v0.11.9`, inclusive. A proof of concept of this vulnerability exists.\n\n### Details\n\nIn vulnerable versions of Pixelfed (versions before 0.11.11), when the API checked the request for permissions to perform a certain behavior, it did not check that the OAuth Application/Client had granted access to those API endpoints, it only checked if the user was authenticated via an access token, and if the user was the owner of the resource or an admin on the instance.\n\nThis meant that an attacker could request an access token for \"read\" permissions to authenticate you with their application, but the access token that they obtained actually could be used for \"write\" or even administrative actions, and the user who granted access to their account had zero knowledge of this elevated access.\n\n#### Proof of Concept\n\n1. Create an access token either via [2-legged OAuth flow](","public_affected_ranges":["ECOSYSTEM: introduced 0.10.4; fixed 0.11.11"]}],"null_published_at":"2026-10-31T22:13:10.047Z","source_updated_at":"2026-09-10T03:50:05.560Z","source_disclosed_at":"2024-02-12T15:17:23.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.415Z"}],"next_cursor":null,"snapshot_revision":"42594"}