{"items":[{"id":"NVI-00007782","kind":"vulnerability","title":"namshi/jose insecure JSON Web Signatures (JWS)","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-hxhc-wmg8-xrqf"],"plain_summary":"OSV carries this publisher advisory for namshi/jose, namshi/jose, namshi/jose, namshi/jose. 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.1.2 for namshi/jose. Confirm the publisher’s latest guidance.","source_ids":["sr-e8a9045c832f78392b2a3c010a91bf5f"],"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":"The original advisory lists fixed boundaries 1.2.2 for namshi/jose. Confirm the publisher’s latest guidance.","source_ids":["sr-e8a9045c832f78392b2a3c010a91bf5f"],"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":"The original advisory lists fixed boundaries 2.0.3 for namshi/jose. Confirm the publisher’s latest guidance.","source_ids":["sr-e8a9045c832f78392b2a3c010a91bf5f"],"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":"The original advisory lists fixed boundaries 2.1.2 for namshi/jose. Confirm the publisher’s latest guidance.","source_ids":["sr-e8a9045c832f78392b2a3c010a91bf5f"],"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-e8a9045c832f78392b2a3c010a91bf5f","url":"https://github.com/advisories/GHSA-hxhc-wmg8-xrqf","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-hxhc-wmg8-xrqf","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:20.434Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-e8a9045c832f78392b2a3c010a91bf5f"],"technology":"namshi/jose","known_exclusions":[],"conditions_summary":"namshi/jose allows the acceptance of unsecure JSON Web Signatures (JWS) by default. The vulnerability arises from the $allowUnsecure flag, which, when set to true during the loading of JWSes, permits tokens signed with 'none' algorithms to be processed. This behavior poses a significant security risk as it could allow an attacker to impersonate users by crafting a valid jwt token.","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 1.1.2"]},{"certainty":"source_listed","source_ids":["sr-e8a9045c832f78392b2a3c010a91bf5f"],"technology":"namshi/jose","known_exclusions":[],"conditions_summary":"namshi/jose allows the acceptance of unsecure JSON Web Signatures (JWS) by default. The vulnerability arises from the $allowUnsecure flag, which, when set to true during the loading of JWSes, permits tokens signed with 'none' algorithms to be processed. This behavior poses a significant security risk as it could allow an attacker to impersonate users by crafting a valid jwt token.","public_affected_ranges":["ECOSYSTEM: introduced 1.2.0; fixed 1.2.2"]},{"certainty":"source_listed","source_ids":["sr-e8a9045c832f78392b2a3c010a91bf5f"],"technology":"namshi/jose","known_exclusions":[],"conditions_summary":"namshi/jose allows the acceptance of unsecure JSON Web Signatures (JWS) by default. The vulnerability arises from the $allowUnsecure flag, which, when set to true during the loading of JWSes, permits tokens signed with 'none' algorithms to be processed. This behavior poses a significant security risk as it could allow an attacker to impersonate users by crafting a valid jwt token.","public_affected_ranges":["ECOSYSTEM: introduced 2.0.0; fixed 2.0.3"]},{"certainty":"source_listed","source_ids":["sr-e8a9045c832f78392b2a3c010a91bf5f"],"technology":"namshi/jose","known_exclusions":[],"conditions_summary":"namshi/jose allows the acceptance of unsecure JSON Web Signatures (JWS) by default. The vulnerability arises from the $allowUnsecure flag, which, when set to true during the loading of JWSes, permits tokens signed with 'none' algorithms to be processed. This behavior poses a significant security risk as it could allow an attacker to impersonate users by crafting a valid jwt token.","public_affected_ranges":["ECOSYSTEM: introduced 2.1.0; fixed 2.1.2"]}],"null_published_at":"2026-10-31T22:13:18.634Z","source_updated_at":"2024-12-02T05:44:05.646Z","source_disclosed_at":"2024-05-17T22:31:42.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.434Z"}],"next_cursor":null,"snapshot_revision":"42594"}