https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-03T15:28:48.446014+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/certfr-2024-avi-0145 certfr-2024-avi-0145 — De multiples vulnérabilités ont été découvertes dans <span class="textit">les produits IBM</span>. Certaines d'entre el… 2026-10-03T15:28:48.530774+00:00 certfr-2024-avi-0145 https://cve.radiocsirt.org/vuln/euvd-2026-229573 EUVD-2026-229573 2026-10-03T15:28:48.530832+00:00 EUVD-2026-229573 https://cve.radiocsirt.org/vuln/fkie_cve-2022-23539 fkie_cve-2022-23539 2026-10-03T15:28:48.530855+00:00

Versions `<=8.5.1` of `jsonwebtoken` library could be misconfigured so that legacy, insecure key types are used for signature verification. For example, DSA keys could be used with the RS256 algorithm. You are affected if you are using an algorithm and a key type other than a combination listed in the GitHub Security Advisory as unaffected. This issue has been fixed, please update to version 9.0.0. This version validates for asymmetric key type and algorithm combinations. Please refer to the above mentioned algorithm / key type combinations for the valid secure configuration. After updating to version 9.0.0, if you still intend to continue with signing or verifying tokens using invalid key type/algorithm value combinations, you’ll need to set the `allowInvalidAsymmetricKeyTypes` option to `true` in the `sign()` and/or `verify()` functions.

 https://cve.radiocsirt.org/vuln/ghsa-8cf7-32gw-wr33 GHSA-8cf7-32gw-wr33 — jsonwebtoken unrestricted key type could lead to legacy keys usage 2026-10-03T15:28:48.530917+00:00

Affected: npm: jsonwebtoken

# Overview

Versions `<=8.5.1` of `jsonwebtoken` library could be misconfigured so that legacy, insecure key types are used for signature verification. For example, DSA keys could be used with the RS256 algorithm.

# Am I affected?

You are affected if you are using an algorithm and a key type other than the combinations mentioned below

| Key type | algorithm | |----------|------------------------------------------| | ec | ES256, ES384, ES512 | | rsa | RS256, RS384, RS512, PS256, PS384, PS512 | | rsa-pss | PS256, PS384, PS512 |

And for Elliptic Curve algorithms:

| `alg` | Curve | |-------|------------| | ES256 | prime256v1 | | ES384 | secp384r1 | | ES512 | secp521r1 |

# How do I fix it?

Update to version 9.0.0. This version validates for asymmetric key type and algorithm combinations. Please refer to the above mentioned algorithm / key type combinations for the valid secure configuration. After updating to version 9.0.0, If you still intend to continue with signing or verifying tokens using invalid key type/algorithm value combinations, you’ll need to set the `allowInvalidAsymmetricKeyTypes` option to `true` in the `sign()` and/or `verify()` functions.

# Will the fix impact my users?

There will be no impact, if you update to version 9.0.0 and you already use a valid secure combination of key type and algorithm. Otherwise, use the `allowInvalidAsymmetricKeyTypes`…

 https://cve.radiocsirt.org/vuln/gsd-2022-23539 gsd-2022-23539 2026-10-03T15:28:48.531013+00:00 gsd-2022-23539 https://cve.radiocsirt.org/vuln/rhsa-2023:3265 RHSA-2023:3265 — Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.12.3 Security and Bug fix update 2026-10-03T15:28:48.531034+00:00

jsonwebtoken: Unrestricted key type could lead to legacy keys usagen express: "qs" prototype poisoning causes the hang of the node process

 https://cve.radiocsirt.org/vuln/wid-sec-w-2023-0218 WID-SEC-W-2023-0218 — IBM Integration Bus: Mehrere Schwachstellen 2026-10-03T15:28:48.531067+00:00

Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in IBM Integration Bus ausnutzen, um beliebigen Programmcode auszuführen oder Sicherheitsvorkehrungen zu umgehen.