{"answers":{"affected":"2 open source packages ship an affected version, including pyload-ng.","exploited":"There is no known exploitation of GHSA-fj52-5g4h-gmq8 in the wild and no public exploit code.","fix":"No fix has been published for GHSA-fj52-5g4h-gmq8 yet. Limit exposure of the affected software until one is available.","what":"GHSA-fj52-5g4h-gmq8 is a missing authorization vulnerability in pyload-ng, published on 14 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-fj52-5g4h-gmq8 and fix it if it is affected.\n\nWhat it is: GHSA-fj52-5g4h-gmq8 is a missing authorization vulnerability in pyload-ng, published on 14 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-fj52-5g4h-gmq8 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- pyload-ng (PyPI): affected all versions up to 0.5.0b3.dev97; no fix listed\n- pyload-ng (PyPI): affected all versions up to 0.5.0b3.dev97; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-fj52-5g4h-gmq8/ (Markdown: https://insights.sbomify.com/GHSA-fj52-5g4h-gmq8/index.md)","id":"GHSA-fj52-5g4h-gmq8","markdown":"https://insights.sbomify.com/GHSA-fj52-5g4h-gmq8/index.md","name":"GHSA-fj52-5g4h-gmq8","record":{"aliases":[],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"pyLoad download manager","requires_auth":"low_privilege","summary":"Attackers with valid sessions retain access to restricted data after permission revocation due to missing session invalidation in pyLoad.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Summary\nThe `pyload` application does not properly invalidate or modify sessions upon changes made to a user's permissions.\n\n### Details\nWhenever an administrator changes the permissions a specific account has, they do not expect that account still being able to access data that their new permissions do not allow. This is not the case for the `pyload` application, as a user with a valid session can still perform the actions.\n\n### PoC\nTake a user with all the permissions, as shown below.\n![image](https://user-images.githubusercontent.com/44903767/294956335-0e4da84f-bf9a-42c8-87f1-f5ff35967c63.png)\n\nWe now log in as this user.\n![image](https://user-images.githubusercontent.com/44903767/294956539-ac6805fe-957d-4289-8ca9-2f3b6b2878a3.png)\n\nLet us now take away all the permissions.\n![image](https://user-images.githubusercontent.com/44903767/294956689-757e6e08-03fd-42eb-b4a5-1ceefa6c24ed.png)\n\nThe logged in session can still be used to access everything in the application.\n![image](https://user-images.githubusercontent.com/44903767/294956943-fa0f23c0-a28c-4eed-89d6-1cc074feda6d.png)\n\n### Impact\nShould permissions be taken away, then the user is expected not to be able to execute the actions belonging to those actions anymore.","ecosystems":["PyPI"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":false,"headline":"pyLoad's Session Not Invalidated After Permission Changes","id":"GHSA-fj52-5g4h-gmq8","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.5.0b3.dev97"],"package":"pyload-ng","purl":null,"source":"GHSA-fj52-5g4h-gmq8"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.5.0b3.dev97"],"package":"pyload-ng","purl":"pkg:pypi/pyload-ng","source":"GHSA-fj52-5g4h-gmq8"}],"products":null,"published":"2026-04-14","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers with valid sessions retain access to restricted data after permission revocation due to missing session invalidation in pyLoad.","url":"https://insights.sbomify.com/GHSA-fj52-5g4h-gmq8/"}