{"id":"CVE-2025-64099","aliases":["EUVD-2025-131956","GHSA-39hr-239p-fhqc"],"status":"published","title":"OpenAM allows use of arbitrary OIDC requested claims values in id_token and user_info","description":"Open Access Management (OpenAM) is an access management solution. In versions prior to 16.0.0, if the \"claims_parameter_supported\" parameter is activated, it is possible, thanks to the \"oidc-claims-extension.groovy\" script, to inject the value of one's choice into a claim contained in the id_token or in the user_info. In the request of an authorize function, a claims parameter containing a JSON file can be injected. This JSON file allows attackers to customize the claims returned by the \"id_token\" and \"user_info\" files. This allows for a very wide range of vulnerabilities depending on how clients use claims. For example, if some clients rely on an email field to identify a user, an attacker can choose the email address they want, and therefore assume any identity they choose. Version 16.0.0 fixes the issue.","severity":{"version":"4.0","score":8.1,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-09","score":0.00353,"percentile":0.29182,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-74","CWE-94"],"published":"2025-11-12T18:57:34Z","modified":"2026-10-18T20:10:00Z","fixes":[{"ecosystem":"Maven","package":"org.openidentityplatform.openam:openam-oauth2","fixed_in":["16.0.3"],"sources":["ghsa","osv"]}],"affected":[{"source":"ghsa","ecosystem":"Maven","package":"org.openidentityplatform.openam:openam-oauth2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.0.3"}]}]},{"source":"osv","ecosystem":"Maven","package":"org.openidentityplatform.openam:openam-oauth2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.0.3"}]}],"versions":["14.5.2","14.5.3","14.5.4","14.6.1","14.6.2","14.6.3","14.6.4","14.6.5","14.6.6","14.7.0","14.7.1","14.7.2","14.7.3","14.7.4","14.8.1","14.8.2","14.8.3","14.8.4","15.0.0","15.0.1","15.0.2","15.0.3","15.0.4","15.1.0","15.1.1","15.1.2","15.1.3","15.1.4","15.1.5","15.1.6","15.2.0","15.2.1","15.2.2","16.0.1","16.0.2"]}],"products":[{"vendor":"openidentityplatform","product":"openam"}],"references":[{"url":"https://github.com/OpenIdentityPlatform/OpenAM/security/advisories/GHSA-39hr-239p-fhqc","tags":["x_refsource_CONFIRM","web"]},{"url":"https://github.com/OpenIdentityPlatform/OpenAM/commit/4254b34b2b8b4867f2e7fccfac73904213d48510","tags":["web"]},{"url":"https://github.com/OpenIdentityPlatform/OpenAM/releases/tag/16.0.3","tags":["web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-64099","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-39hr-239p-fhqc"},{"url":"https://github.com/OpenIdentityPlatform/OpenAM","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2025-64099","title":"OpenAM allows use of arbitrary OIDC requested claims values in id_token and user_info","description":"Open Access Management (OpenAM) is an access management solution. In versions prior to 16.0.0, if the \"claims_parameter_supported\" parameter is activated, it is possible, thanks to the \"oidc-claims-extension.groovy\" script, to inject the value of one's choice into a claim contained in the id_token or in the user_info. In the request of an authorize function, a claims parameter containing a JSON file can be injected. This JSON file allows attackers to customize the claims returned by the \"id_token\" and \"user_info\" files. This allows for a very wide range of vulnerabilities depending on how clients use claims. For example, if some clients rely on an email field to identify a user, an attacker can choose the email address they want, and therefore assume any identity they choose. Version 16.0.0 fixes the issue.","status":"published","published":"2025-11-12T18:57:34.036Z","modified":"2025-11-12T21:04:04.048Z","cvss":[{"version":"4.0","score":8.1,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U","level":"high","assessor":"cna"}],"cwes":["CWE-74"],"updated_at":"2026-11-02T14:32:46.750177Z"}],"euvd":[{"id":"EUVD-2025-131956","description":"Open Access Management (OpenAM) is an access management solution. In versions prior to 16.0.0, if the \"claims_parameter_supported\" parameter is activated, it is possible, thanks to the \"oidc-claims-extension.groovy\" script, to inject the value of one's choice into a claim contained in the id_token or in the user_info. In the request of an authorize function, a claims parameter containing a JSON file can be injected. This JSON file allows attackers to customize the claims returned by the \"id_token\" and \"user_info\" files. This allows for a very wide range of vulnerabilities depending on how clients use claims. For example, if some clients rely on an email field to identify a user, an attacker can choose the email address they want, and therefore assume any identity they choose. Version 16.0.0 fixes the issue.","status":"published","published":"2025-11-12T18:57:34Z","modified":"2025-11-12T21:04:04Z","cvss":[{"version":"4.0","score":8.1,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U","level":"high"}],"updated_at":"2026-11-02T19:49:17.986196Z"}],"ghsa":[{"id":"GHSA-39hr-239p-fhqc","title":"OpenAM: Using arbitrary OIDC requested claims values in id_token and user_info is allowed ","description":"### Summary\nIf the \"claims_parameter_supported\" parameter is activated, it is possible through the \"oidc-claims-extension.groovy\" script, to inject the value of choice into a claim contained in the id_token or in the user_info.\nAuthorization function requests do not prevent a claims parameter containing a JSON file to be injected. This JSON file allows users to customize claims returned by the \"id_token\" and \"user_info\" files.\nThis allows for a very wide range of vulnerabilities depending on how clients use claims. For example, if some clients rely on an email field to identify a user, users can choose to entera any email address, and therefore assume any chosen identity.","status":"published","published":"2025-11-12T21:27:22Z","modified":"2025-11-15T03:12:53Z","cvss":[{"version":"4.0","score":8.1,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U","level":"high"}],"cwes":["CWE-74","CWE-94"],"updated_at":"2026-11-02T14:39:08.983925Z"}],"nvd":[{"id":"CVE-2025-64099","description":"Open Access Management (OpenAM) is an access management solution. In versions prior to 16.0.0, if the \"claims_parameter_supported\" parameter is activated, it is possible, thanks to the \"oidc-claims-extension.groovy\" script, to inject the value of one's choice into a claim contained in the id_token or in the user_info. In the request of an authorize function, a claims parameter containing a JSON file can be injected. This JSON file allows attackers to customize the claims returned by the \"id_token\" and \"user_info\" files. This allows for a very wide range of vulnerabilities depending on how clients use claims. For example, if some clients rely on an email field to identify a user, an attacker can choose the email address they want, and therefore assume any identity they choose. Version 16.0.0 fixes the issue.","status":"published","published":"2025-11-12T19:15:38.087Z","modified":"2026-10-18T20:10:00.11Z","cvss":[{"version":"4.0","score":8.1,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"high","assessor":"secondary"}],"cwes":["CWE-74"],"updated_at":"2026-11-02T14:11:43.650381Z"}],"osv":[{"id":"GHSA-39hr-239p-fhqc","title":"OpenAM: Using arbitrary OIDC requested claims values in id_token and user_info is allowed ","description":"### Summary\nIf the \"claims_parameter_supported\" parameter is activated, it is possible through the \"oidc-claims-extension.groovy\" script, to inject the value of choice into a claim contained in the id_token or in the user_info.\nAuthorization function requests do not prevent a claims parameter containing a JSON file to be injected. This JSON file allows users to customize claims returned by the \"id_token\" and \"user_info\" files.\nThis allows for a very wide range of vulnerabilities depending on how clients use claims. For example, if some clients rely on an email field to identify a user, users can choose to entera any email address, and therefore assume any chosen identity.","status":"published","published":"2025-11-12T21:27:22Z","modified":"2025-11-15T03:34:07.748195Z","cvss":[{"version":"4.0","score":8.1,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U","level":"high"}],"cwes":["CWE-74","CWE-94"],"updated_at":"2026-11-02T15:46:35.406455Z"}]}}