{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62382 exists.","fix":"No fix has been published for CVE-2026-62382 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-62382 is a medium-severity authentication bypass vulnerability in pglombardo PasswordPusher, published on 22 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-62382 and fix it if it is affected.\n\nWhat it is: CVE-2026-62382 is a medium-severity authentication bypass vulnerability in pglombardo PasswordPusher, published on 22 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62382 exists.\n\nAffected product: pglombardo PasswordPusher. No package-level version data is available, so check the vendor advisory linked from the reference page.\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/CVE-2026-62382/ (Markdown: https://insights.sbomify.com/CVE-2026-62382/index.md)","id":"CVE-2026-62382","markdown":"https://insights.sbomify.com/CVE-2026-62382/index.md","name":"CVE-2026-62382","record":{"aliases":["GHSA-h7j9-p76m-fhvx","GHSA-jf2m-hpj9-4qx2"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"PasswordPusher","requires_auth":"none","summary":"Attackers can delete anonymous password pushes without authorization due to a null comparison flaw in ownership checks.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"PasswordPusher versions v1.45.11 through v2.9.5 contain an improper authorization vulnerability in the push deletion logic. The ownership check compares @push.user against current_user; for an anonymously created push both values are nil, and Ruby evaluates nil == nil as true, so the check passes and the deletable_by_viewer restriction is never enforced. An attacker who knows only the secret URL can permanently delete an anonymous push even when the creator disabled viewer deletion and even without the passphrase. Only deployments that allow anonymous pushes (the default) are affected. The issue is fixed in v2.9.6.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2026/CVE-2026-62382.yaml","stars":null,"title":"PasswordPusher v1.45.11-v2.9.5 - Unauthenticated Anonymous Push Deletion via Ownership Bypass"}],"tier":"weaponised"},"has_fix":false,"headline":"PasswordPusher before v2.9.6 Authentication Bypass via Null Comparison","id":"CVE-2026-62382","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"nltk IPIPANCorpusReader Symlink Arbitrary File Read","id":"CVE-2026-62383"},"packages":[],"prev":{"headline":"luci-lib-px5g 2040-bit Certificate Signing Heap Buffer Overflow","id":"CVE-2026-62381"},"products":["PasswordPusher"],"published":"2026-08-22","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-31","vendors":["pglombardo"]},"summary":"Attackers can delete anonymous password pushes without authorization due to a null comparison flaw in ownership checks.","url":"https://insights.sbomify.com/CVE-2026-62382/"}