https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-06T18:14:41.292304+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2025-04295 bdu:2025-04295 2026-10-06T18:14:41.813567+00:00 bdu:2025-04295 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0692 certfr-2024-avi-0692 — De multiples vulnérabilités ont été découvertes dans les produits IBM. Certaines d'entre elles permettent à un attaquan… 2026-10-06T18:14:41.813621+00:00 certfr-2024-avi-0692 https://cve.radiocsirt.org/vuln/euvd-2026-221653 EUVD-2026-221653 2026-10-06T18:14:41.813654+00:00 EUVD-2026-221653 https://cve.radiocsirt.org/vuln/fkie_cve-2023-23612 fkie_cve-2023-23612 2026-10-06T18:14:41.813675+00:00

OpenSearch is an open source distributed and RESTful search engine. OpenSearch uses JWTs to store role claims obtained from the Identity Provider (IdP) when the authentication backend is SAML or OpenID Connect. There is an issue in how those claims are processed from the JWTs where the leading and trailing whitespace is trimmed, allowing users to potentially claim roles they are not assigned to if any role matches the whitespace-stripped version of the roles they are a member of. This issue is only present for authenticated users, and it requires either the existence of roles that match, not considering leading/trailing whitespace, or the ability for users to create said matching roles. In addition, the Identity Provider must allow leading and trailing spaces in role names. OpenSearch 1.0.0-1.3.7 and 2.0.0-2.4.1 are affected. Users are advised to upgrade to OpenSearch 1.3.8 or 2.5.0. There are no known workarounds for this issue.

 https://cve.radiocsirt.org/vuln/ghsa-864v-6qj7-62qj GHSA-864v-6qj7-62qj — Issue with whitespace in JWT roles in OpenSearch 2026-10-06T18:14:41.813723+00:00

Affected: Maven: org.opensearch.plugin:opensearch-security

### Advisory title: Issue with whitespace in JWT roles

### Affected versions: OpenSearch 1.0.0-1.3.7 and 2.0.0-2.4.1

### Patched versions: OpenSearch 1.3.8 and 2.5.0

### Impact: OpenSearch uses JWTs to store role claims obtained from the Identity Provider (IdP) when the authentication backend is SAML or OpenID Connect. There is an issue in how those claims are processed from the JWTs where the leading and trailing whitespace is trimmed, allowing users to potentially claim roles they are not assigned to if any role matches the whitespace-stripped version of the roles they are a member of.

This issue is only present for authenticated users, and it requires either the existence of roles that match, not considering leading/trailing whitespace, or the ability for users to create said matching roles. In addition, the Identity Provider must allow leading and trailing spaces in role names.

### Patches: OpenSearch versions 1.3.8 and 2.5.0 contain a fix for this issue.

### For more information: If you have any questions or comments about this advisory, please contact AWS/Amazon Security via our issue reporting page (https://aws.amazon.com/security/vulnerability-reporting/) or directly via email to [aws-security@amazon.com](mailto:aws-security@amazon.com). Please do not create a public GitHub issue.

 https://cve.radiocsirt.org/vuln/gsd-2023-23612 gsd-2023-23612 2026-10-06T18:14:41.813789+00:00 gsd-2023-23612 https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-23612 UBUNTU-CVE-2023-23612 2026-10-06T18:14:41.813816+00:00

Affected: Ubuntu:24.04:LTS: opensearch

OpenSearch is an open source distributed and RESTful search engine. OpenSearch uses JWTs to store role claims obtained from the Identity Provider (IdP) when the authentication backend is SAML or OpenID Connect. There is an issue in how those claims are processed from the JWTs where the leading and trailing whitespace is trimmed, allowing users to potentially claim roles they are not assigned to if any role matches the whitespace-stripped version of the roles they are a member of. This issue is only present for authenticated users, and it requires either the existence of roles that match, not considering leading/trailing whitespace, or the ability for users to create said matching roles. In addition, the Identity Provider must allow leading and trailing spaces in role names. OpenSearch 1.0.0-1.3.7 and 2.0.0-2.4.1 are affected. Users are advised to upgrade to OpenSearch 1.3.8 or 2.5.0. There are no known workarounds for this issue.