Threat Intelligence Database
Comprehensive database of the latest cyber threats affecting organizations worldwide. Filter and search to find specific threat intelligence relevant to your organization.
Stop chasing alerts. Route them.
Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.
Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)
API access activates after upgrading in Console -> Billing.
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.
Filter Threats
Narrow down the results by type, severity, or affected countries
Threat Intelligence
Click on any threat for detailed analysis and mitigation recommendations
CVE-2026-47192: CWE-347: Improper Verification of Cryptographic Signature in siemens kasCVE-2026-47192 0 CVE-2026-47192 is a low-severity vulnerability in the Siemens kas tool versions 4.8 up to but not including 5.3. The flaw involves improper verification of cryptographic signatures, where kas processes repository configurations before validating their signatures. Under specific conditions involving repository control by an attacker and certain configuration settings, an attacker could replace a referenced repository with a malicious one. Patches addressing this issue were released in kas version 5.3. A recommended workaround is to pin the expected signature key via its fingerprint when storing it as a file in a repository. Join the discussion | CVE Database V5 | 08/14/2026, 16:41:27 UTC Added: 08/14/2026, 17:13:51 UTC |
CVE-2026-47191: CWE-347: Improper Verification of Cryptographic Signature in siemens kasCVE-2026-47191 0 CVE-2026-47191 is a low severity vulnerability in Siemens kas, a setup tool for bitbake-based projects. Prior to version 5.3, kas relied solely on git commit IDs (SHA-1 or SHA-256) to verify repository integrity, which could be bypassed if an attacker took over the repository and created a branch with the same name. This flaw allows users to be tricked into checking out malicious code. The issue primarily affects SHA-256 commit IDs due to the possibility of branch takeover and SHA-1 due to hash collisions. Version 5.3 addresses this vulnerability. Workarounds include avoiding sole reliance on commit IDs, validating cryptographically signed commits or tags, or using mirrored repositories with verified integrity. Join the discussion | CVE Database V5 | 08/14/2026, 16:35:48 UTC Added: 08/14/2026, 16:42:36 UTC |
Showing 1 to 2 of 2 results