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
0 CVE-2026-77310 is a Server-Side Request Forgery (SSRF) vulnerability in the jackson-databind library of FasterXML. The vulnerability arises from the deserialization process invoking java.net.InetAddress.getByName() on attacker-controlled input, leading to eager DNS resolution. This can enable DNS-based SSRF and internal host enumeration. The issue affects multiple release lines prior to versions 2.18.9, 2.21.5, 2.22.1, 3.1.5, and 3.2.1, where it has been fixed. Join the discussion | CVE Database V5 | 08/24/2026, 19:24:59 UTC Added: 08/24/2026, 19:37:53 UTC |
CVE-2026-59889 is an authorization bypass vulnerability in FasterXML jackson-databind affecting versions prior to 2.21.5, 2.22.1, 3.1.5, and 3.2.1. It occurs because the processUnwrapped() method does not enforce the @JsonView authorization guard on container properties annotated with @JsonUnwrapped, allowing attacker-controlled JSON to overwrite privileged fields under a more restrictive view. This can lead to write-side mass-assignment and privilege escalation, such as an attacker assigning themselves admin roles or elevated privileges. The issue affects both 2.x and 3.x branches and variants including nested unwrapped properties and builder-based deserializers. A patch is available that adds the missing view guard to processUnwrapped(), closing all known bypass variants. Join the discussion | CVE Database V5 | 07/21/2026, 22:00:43 UTC Added: 07/14/2026, 20:33:37 UTC |
This security update addresses multiple vulnerabilities in jackson-annotations, jackson-core, and jackson-databind libraries. The issues include bypasses of @JsonIgnoreProperties exclusions, unauthorized writes to @JsonView restricted fields due to missing view guards, and bypasses of @JsonIgnore restrictions on Java Records caused by mismatches in property renaming and ignore-filtering. The update advances all three components to version 2.18.9, which includes fixes for these vulnerabilities. Join the discussion | GCVE Database | 07/18/2026, 12:43:11 UTC Added: 09/17/2026, 01:59:06 UTC |
0 A vulnerability in FasterXML jackson-databind versions from 2.15.0 up to but not including 2.18.8, 2.21.4, and 3.1.4 allows Java Records using a PropertyNamingStrategy to bypass the @JsonIgnore annotation. This occurs because the ignored component is recorded under its original name before the naming strategy renames the JSON key, enabling assignment to the Record constructor parameter. The issue is fixed starting from versions 2.18.8, 2.21.4, and 3.1.4. Join the discussion | CVE Database V5 | 07/15/2026, 00:00:00 UTC Added: 07/14/2026, 17:19:02 UTC |
jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.21.0 until 2.21.4 and 3.1.4, UnwrappedPropertyHandler.processUnwrappedCreatorProperties() replays buffered JSON into creator parameters but never consults prop.visibleInView(activeView). The normal property-based creator path gates creator properties on the active view, but this unwrapped-creator replay path bypasses that check, so a constructor parameter annotated with both @JsonView(AdminView.class) and @JsonUnwrapped is populated from attacker JSON even when a more restrictive view is active. This vulnerability is fixed in 2.21.4 and 3.1.4. Join the discussion | CVE Database V5 | 06/23/2026, 21:02:07 UTC Added: 06/23/2026, 21:54:20 UTC |
0 jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.13.0 until 2.14.0, a potential Denial-of-Service exists when attacker sends deeply nested JSON if (and only if) the service reads deeply nested (1000s of levels) JSON as JsonNode (ObjectMapper.readTree()) and writes out same (or modifided) node using JsonNode.toString(). This can consume significant amount of resources with concurrent relatively small requests (1000 nested arrays is 2kB). This vulnerability is fixed in 2.14.0. Join the discussion | CVE Database V5 | 06/23/2026, 21:00:20 UTC Added: 06/23/2026, 21:09:22 UTC |
0 jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.10.0 until 2.18.8, 2.21.4, and 3.1.4, jackson-databind's PolymorphicTypeValidator (PTV) is the primary safety mechanism guarding polymorphic deserialization. When polymorphic typing is enabled and a type identifier contains generic parameters (i.e. the type ID string contains <), DatabindContext._resolveAndValidateGeneric() validates only the raw container class name (the substring before <) against the configured PTV. If the container type is approved, the method parses the full canonical type string via TypeFactory.constructFromCanonical() and returns the fully parameterized type without ever validating the nested type arguments against the PTV. The nested type arguments are then resolved, instantiated, and populated as beans during deserialization. An attacker who controls the type ID can therefore place a denied class as a generic type parameter of an allowed container — for example java.util.ArrayList<com.evil.Gadget> when only java.util.ArrayList is allow-listed. The container passes the PTV check; com.evil.Gadget is loaded via Class.forName(name, true, loader), instantiated, and its properties are set from attacker-controlled JSON. This completely bypasses an explicitly configured PTV allow-list. This vulnerability is fixed in 2.18.8, 2.21.4, and 3.1.4. Join the discussion | CVE Database V5 | 06/23/2026, 20:56:36 UTC Added: 06/23/2026, 21:09:22 UTC |
0 jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.10.0 until 2.18.8, 2.21.4, and 3.1.4, BasicPolymorphicTypeValidator.Builder.allowIfSubTypeIsArray() allowlists any array type based only on clazz.isArray(), without validating the array's component (element) type against the configured allowlist. A PTV built with allowIfSubTypeIsArray() plus an explicit concrete-type allowlist therefore still permits EvilType[] even though EvilType is not allowlisted. When Jackson deserializes the elements and no per-element type IDs are present, it instantiates the component type directly with no further PTV check, bypassing the allowlist. This vulnerability is fixed in 2.18.8, 2.21.4, and 3.1.4. Join the discussion | CVE Database V5 | 06/23/2026, 20:53:52 UTC Added: 06/23/2026, 21:09:22 UTC |
0 jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.0.0 until 2.18.8, 2.21.4, and 3.1.4, JDKFromStringDeserializer constructed InetSocketAddress with new InetSocketAddress(host, port), which performs eager DNS name resolution for hostname inputs at deserialization time. An application that binds untrusted JSON into a type containing an InetSocketAddress field issues an attacker-chosen DNS query during readValue, before any application-level validation or connect logic. The fix uses InetSocketAddress.createUnresolved(host, port), deferring DNS to an explicit connect. This vulnerability is fixed in 2.18.8, 2.21.4, and 3.1.4. Join the discussion | CVE Database V5 | 06/23/2026, 20:51:50 UTC Added: 06/23/2026, 21:09:22 UTC |
0 jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.8.0 until 2.18.9, 2.21.5, and 3.1.4, in BeanDeserializerBase.createContextual(), per-property @JsonIgnoreProperties exclusions are applied by _handleByNameInclusion(), producing a contextual deserializer whose BeanPropertyMap has the ignored properties removed. The subsequent per-property case-insensitivity block (triggered by @JsonFormat(ACCEPT_CASE_INSENSITIVE_PROPERTIES)) rebuilds from this._beanProperties (the original, unfiltered map) instead of contextual._beanProperties, then overwrites the filtered map — restoring every property _handleByNameInclusion had just removed. The ignored property becomes writable again. This vulnerability is fixed in 2.18.9, 2.21.5, and 3.1.4. Join the discussion | CVE Database V5 | 06/23/2026, 20:50:25 UTC Added: 06/23/2026, 21:09:22 UTC |
Showing 1 to 10 of 12 results