BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-54514High confidence

jackson-databind: InetSocketAddress deserialization triggers eager DNS resolution (SSRF)

FasterXML · jackson-databind

Official source article: GitHub GHSA-HGJ6-7826-R7M5 ↗. Check the applicable product and release in the original source.

5.3MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 105 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.37% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs FasterXML jackson-databind and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 105 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 4 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcejackson-databindAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 8 Oct 2026
Debian bookwormbookworm · sourcejackson-databindAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 8 Oct 2026
Debian forkyforky · sourcejackson-databindAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 8 Oct 2026
Debian sidsid · sourcejackson-databindAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 8 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivejackson-databindUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 7 Oct 2026
Open-source package ranges10 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
Mavencom.fasterxml.jackson.core:jackson-databindECOSYSTEM: introduced 2.0.0; fixed 2.18.82.18.8OSV record ↗aggregator derived · 10 Sep 2026
Mavencom.fasterxml.jackson.core:jackson-databindECOSYSTEM: introduced 2.19.0; fixed 2.21.42.21.4OSV record ↗aggregator derived · 10 Sep 2026
Mavencom.fasterxml.jackson.core:jackson-databindECOSYSTEM: introduced 3.0.0; fixed 3.1.43.1.4OSV record ↗aggregator derived · 10 Sep 2026
Maventools.jackson.core:jackson-databindECOSYSTEM: introduced 2.19.0; fixed 2.21.42.21.4OSV record ↗aggregator derived · 10 Sep 2026
Maventools.jackson.core:jackson-databindECOSYSTEM: introduced 3.0.0; fixed 3.1.43.1.4OSV record ↗aggregator derived · 10 Sep 2026
mavencom.fasterxml.jackson.core:jackson-databind>= 2.0.0, < 2.18.82.18.8GitHub advisory ↗upstream repository advisory · 20 Jul 2026
mavencom.fasterxml.jackson.core:jackson-databind>= 2.19.0, < 2.21.42.21.4GitHub advisory ↗upstream repository advisory · 20 Jul 2026
mavencom.fasterxml.jackson.core:jackson-databind>= 3.0.0, < 3.1.43.1.4GitHub advisory ↗upstream repository advisory · 20 Jul 2026
maventools.jackson.core:jackson-databind>= 2.19.0, < 2.21.42.21.4GitHub advisory ↗upstream repository advisory · 20 Jul 2026
maventools.jackson.core:jackson-databind>= 3.0.0, < 3.1.43.1.4GitHub advisory ↗upstream repository advisory · 20 Jul 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-54514 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityjackson-databind: jackson-databind: Information Disclosure via Eager DNS Resolution
101 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • jackson-databind as a component of Cryostat 4
  • jenkins-2-plugins.src as a component of OpenShift Developer Tools and Services
  • jenkins.src as a component of OpenShift Developer Tools and Services
  • ocp-tools-4/jenkins-rhel8 as a component of OpenShift Developer Tools and Services
  • ocp-tools-4/jenkins-rhel9 as a component of OpenShift Developer Tools and Services
  • openshift-serverless-1/kn-ekb-dispatcher-rhel9 as a component of OpenShift Serverless
  • openshift-serverless-1/kn-ekb-receiver-rhel9 as a component of OpenShift Serverless
  • openshift-serverless-1/kn-eventing-integrations-aws-ddb-streams-source-rhel9 as a component of OpenShift Serverless
  • openshift-serverless-1/kn-eventing-integrations-aws-s3-sink-rhel9 as a component of OpenShift Serverless
  • openshift-serverless-1/kn-eventing-integrations-aws-s3-source-rhel9 as a component of OpenShift Serverless
  • openshift-serverless-1/kn-eventing-integrations-aws-sns-sink-rhel9 as a component of OpenShift Serverless
  • openshift-serverless-1/kn-eventing-integrations-aws-sqs-sink-rhel9 as a component of OpenShift Serverless
Summary
A flaw was found in jackson-databind, a library used for processing JSON data. This vulnerability allows a remote attacker to force the application to perform an attacker-chosen DNS (Domain Name System) query. This occurs when untrusted JSON input containing specific network address information is processed, potentially leading to the disclosure of sensitive network configuration details.
Remediation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-38592

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 105 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

The server follows an attacker-influenced destination, allowing requests to systems or services the attacker cannot reach directly.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The server follows an attacker-influenced destination, allowing requests to systems or services the attacker cannot reach directly.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Server-Side Request Forgery (SSRF) → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-918 ↗

CWE-918: Server-Side Request Forgery (SSRF). The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CLowConfidentiality impact: A successful attack can cause a limited loss.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-918
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-3595IBM QRadar SIEM: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM QRadar SIEM ausnutzen, um beliebigen Programmcode auszuführen, um seine Privilegien zu erhöhen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Dateien zu manipulieren, um einen Cross-Site Scripting Angriff durchzuführen und um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
BSI · German · WID-SEC-2026-3043IBM QRadar SIEM: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM QRadar SIEM ausnutzen, um Sicherheitsvorkehrungen zu umgehen, um seine Privilegien zu erhöhen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Dateien zu manipulieren, um einen Cross-Site Scripting Angriff durchzuführen und um beliebigen Programmcode auszuführen.

Official advisory ↗
BSI · German · WID-SEC-2026-2058FasterXML Jackson: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in FasterXML Jackson ausnutzen, um Schutzmechanismen und Autorisierungsregeln zu umgehen, Daten zu manipulieren, Informationen offenzulegen oder einen Denial-of-Service zu verursachen.

Official advisory ↗
BSI · German · WID-SEC-2026-2867RealObjects PDFreactor: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein Angreifer kann mehrere Schwachstellen in RealObjects PDFreactor ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260624Security Bulletin 24 June 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 24 June 2026, published on 24 June 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1256Multiples vulnérabilités dans les produits IBM

d?id=CVE-2026-53397 Référence CVE CVE-2026-53399 https://www.cve.org/CVERecord?id=CVE-2026-53399 Référence CVE CVE-2026-53550 https://www.cve.org/CVERecord?id=CVE-2026-53550 Référence CVE CVE-2026-53606 https://www.cve.org/CVERecord?id=CVE-2026-53606 Référence CVE CVE-2026-53655 https://www.cve.org/CVERecord?id=CVE-2026-53655 Référence CVE CVE-2026-54371 https://www.cve.org/CVERecord?id=CVE-2026-54371 Référence CVE CVE-2026-54411 https://www.cve.org/CVERecord?id=CVE-2026-54411 Référence CVE CVE-2026-54512 https://www.cve.org/CVERecord?id=CVE-2026-54512 Référence CVE CVE-2026-54513 https://www.cve.org/CVERecord?id=CVE-2026-54513 Référence CVE CVE-2026-54514 https://www.cve.org/CVERecord?id=CVE-2026-54514 Référence CVE CVE-2026-54515 https://www.cve.org/CVERecord?id=CVE-2026-54515 Référence CVE CVE-2026-54516 https://www.cve.org/CVERecord?id=CVE-2026-54516 Référence CVE CVE-2026-54517 https://www.cve.org/CVERecord?id=CVE-2026-54517 Référence CVE CVE-2026-54518 https://www.cve.org/CVERecord?id=CVE-2026-54518 Référence CVE CVE-2026-54874 https://www.cve.org/CVERecord?id=CVE-2026-54874 Référence CVE CVE-2026-5588 https://www.cve.org/CVERecord?id=CVE-2026-5588 Référence CVE CVE-2026-5598 https://www.cve.org/CVERecord?id=CVE-2026-5598 Référence CVE CVE-2026-55995 https://www.cve.org/CVERecord?id=CVE-

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1165Multiples vulnérabilités dans les produits IBM

d?id=CVE-2026-54225 Référence CVE CVE-2026-54264 https://www.cve.org/CVERecord?id=CVE-2026-54264 Référence CVE CVE-2026-54265 https://www.cve.org/CVERecord?id=CVE-2026-54265 Référence CVE CVE-2026-54284 https://www.cve.org/CVERecord?id=CVE-2026-54284 Référence CVE CVE-2026-54297 https://www.cve.org/CVERecord?id=CVE-2026-54297 Référence CVE CVE-2026-54399 https://www.cve.org/CVERecord?id=CVE-2026-54399 Référence CVE CVE-2026-54428 https://www.cve.org/CVERecord?id=CVE-2026-54428 Référence CVE CVE-2026-54512 https://www.cve.org/CVERecord?id=CVE-2026-54512 Référence CVE CVE-2026-54513 https://www.cve.org/CVERecord?id=CVE-2026-54513 Référence CVE CVE-2026-54514 https://www.cve.org/CVERecord?id=CVE-2026-54514 Référence CVE CVE-2026-54515 https://www.cve.org/CVERecord?id=CVE-2026-54515 Référence CVE CVE-2026-54516 https://www.cve.org/CVERecord?id=CVE-2026-54516 Référence CVE CVE-2026-54517 https://www.cve.org/CVERecord?id=CVE-2026-54517 Référence CVE CVE-2026-54518 https://www.cve.org/CVERecord?id=CVE-2026-54518 Référence CVE CVE-2026-5516 https://www.cve.org/CVERecord?id=CVE-2026-5516 Référence CVE CVE-2026-55223 https://www.cve.org/CVERecord?id=CVE-2026-55223 Référence CVE CVE-2026-55760 https://www.cve.org/CVERecord?id=CVE-2026-55760 Référence CVE CVE-2026-55831 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1094Multiples vulnérabilités dans les produits IBM

ecord?id=CVE-2026-54283 Référence CVE CVE-2026-54293 https://www.cve.org/CVERecord?id=CVE-2026-54293 Référence CVE CVE-2026-5435 https://www.cve.org/CVERecord?id=CVE-2026-5435 Référence CVE CVE-2026-54369 https://www.cve.org/CVERecord?id=CVE-2026-54369 Référence CVE CVE-2026-54370 https://www.cve.org/CVERecord?id=CVE-2026-54370 Référence CVE CVE-2026-54475 https://www.cve.org/CVERecord?id=CVE-2026-54475 Référence CVE CVE-2026-5450 https://www.cve.org/CVERecord?id=CVE-2026-5450 Référence CVE CVE-2026-54512 https://www.cve.org/CVERecord?id=CVE-2026-54512 Référence CVE CVE-2026-54513 https://www.cve.org/CVERecord?id=CVE-2026-54513 Référence CVE CVE-2026-54514 https://www.cve.org/CVERecord?id=CVE-2026-54514 Référence CVE CVE-2026-54515 https://www.cve.org/CVERecord?id=CVE-2026-54515 Référence CVE CVE-2026-55153 https://www.cve.org/CVERecord?id=CVE-2026-55153 Référence CVE CVE-2026-55276 https://www.cve.org/CVERecord?id=CVE-2026-55276 Référence CVE CVE-2026-55379 https://www.cve.org/CVERecord?id=CVE-2026-55379 Référence CVE CVE-2026-55380 https://www.cve.org/CVERecord?id=CVE-2026-55380 Référence CVE CVE-2026-55443 https://www.cve.org/CVERecord?id=CVE-2026-55443 Référence CVE CVE-2026-55653 https://www.cve.org/CVERecord?id=CVE-2026-55653 Référence CVE CVE-2026-55655 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0986Multiples vulnérabilités dans les produits IBM

d?id=CVE-2026-50645 Référence CVE CVE-2026-50734 https://www.cve.org/CVERecord?id=CVE-2026-50734 Référence CVE CVE-2026-53916 https://www.cve.org/CVERecord?id=CVE-2026-53916 Référence CVE CVE-2026-53917 https://www.cve.org/CVERecord?id=CVE-2026-53917 Référence CVE CVE-2026-54399 https://www.cve.org/CVERecord?id=CVE-2026-54399 Référence CVE CVE-2026-54428 https://www.cve.org/CVERecord?id=CVE-2026-54428 Référence CVE CVE-2026-54475 https://www.cve.org/CVERecord?id=CVE-2026-54475 Référence CVE CVE-2026-54512 https://www.cve.org/CVERecord?id=CVE-2026-54512 Référence CVE CVE-2026-54513 https://www.cve.org/CVERecord?id=CVE-2026-54513 Référence CVE CVE-2026-54514 https://www.cve.org/CVERecord?id=CVE-2026-54514 Référence CVE CVE-2026-54515 https://www.cve.org/CVERecord?id=CVE-2026-54515 Référence CVE CVE-2026-54516 https://www.cve.org/CVERecord?id=CVE-2026-54516 Référence CVE CVE-2026-54517 https://www.cve.org/CVERecord?id=CVE-2026-54517 Référence CVE CVE-2026-54518 https://www.cve.org/CVERecord?id=CVE-2026-54518 Référence CVE CVE-2026-5588 https://www.cve.org/CVERecord?id=CVE-2026-5588 Référence CVE CVE-2026-5598 https://www.cve.org/CVERecord?id=CVE-2026-5598 Référence CVE CVE-2026-5946 https://www.cve.org/CVERecord?id=CVE-2026-5946 Référence CVE CVE-2026-60147 https://www.cve.org/CVERecord?id=CVE-20

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0933Multiples vulnérabilités dans les produits IBM

d?id=CVE-2026-54276 Référence CVE CVE-2026-54277 https://www.cve.org/CVERecord?id=CVE-2026-54277 Référence CVE CVE-2026-54278 https://www.cve.org/CVERecord?id=CVE-2026-54278 Référence CVE CVE-2026-54279 https://www.cve.org/CVERecord?id=CVE-2026-54279 Référence CVE CVE-2026-54280 https://www.cve.org/CVERecord?id=CVE-2026-54280 Référence CVE CVE-2026-54282 https://www.cve.org/CVERecord?id=CVE-2026-54282 Référence CVE CVE-2026-54283 https://www.cve.org/CVERecord?id=CVE-2026-54283 Référence CVE CVE-2026-54512 https://www.cve.org/CVERecord?id=CVE-2026-54512 Référence CVE CVE-2026-54513 https://www.cve.org/CVERecord?id=CVE-2026-54513 Référence CVE CVE-2026-54514 https://www.cve.org/CVERecord?id=CVE-2026-54514 Référence CVE CVE-2026-54515 https://www.cve.org/CVERecord?id=CVE-2026-54515 Référence CVE CVE-2026-54516 https://www.cve.org/CVERecord?id=CVE-2026-54516 Référence CVE CVE-2026-54517 https://www.cve.org/CVERecord?id=CVE-2026-54517 Référence CVE CVE-2026-54518 https://www.cve.org/CVERecord?id=CVE-2026-54518 Référence CVE CVE-2026-54530 https://www.cve.org/CVERecord?id=CVE-2026-54530 Référence CVE CVE-2026-54531 https://www.cve.org/CVERecord?id=CVE-2026-54531 Référence CVE CVE-2026-54651 https://www.cve.org/CVERecord?id=CVE-2026-54651 Référence CVE CVE-2026-5598 https://www.cve.org/CVERecord?id=C

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0914Multiples vulnérabilités dans Oracle Database Server

ord?id=CVE-2026-47039 Référence CVE CVE-2026-47040 https://www.cve.org/CVERecord?id=CVE-2026-47040 Référence CVE CVE-2026-47045 https://www.cve.org/CVERecord?id=CVE-2026-47045 Référence CVE CVE-2026-47046 https://www.cve.org/CVERecord?id=CVE-2026-47046 Référence CVE CVE-2026-47060 https://www.cve.org/CVERecord?id=CVE-2026-47060 Référence CVE CVE-2026-47061 https://www.cve.org/CVERecord?id=CVE-2026-47061 Référence CVE CVE-2026-4738 https://www.cve.org/CVERecord?id=CVE-2026-4738 Référence CVE CVE-2026-54512 https://www.cve.org/CVERecord?id=CVE-2026-54512 Référence CVE CVE-2026-54513 https://www.cve.org/CVERecord?id=CVE-2026-54513 Référence CVE CVE-2026-54514 https://www.cve.org/CVERecord?id=CVE-2026-54514 Référence CVE CVE-2026-54515 https://www.cve.org/CVERecord?id=CVE-2026-54515 Référence CVE CVE-2026-54516 https://www.cve.org/CVERecord?id=CVE-2026-54516 Référence CVE CVE-2026-54517 https://www.cve.org/CVERecord?id=CVE-2026-54517 Référence CVE CVE-2026-54518 https://www.cve.org/CVERecord?id=CVE-2026-54518 Référence CVE CVE-2026-60175 https://www.cve.org/CVERecord?id=CVE-2026-60175 Référence CVE CVE-2026-61211 https://www.cve.org/CVERecord?id=CVE-2026-61211 Référence CVE CVE-2026-7383 https://www.cve.org/CVERecord?id=CVE-2026-7383 Référence CVE CVE-2026-9076 https://www.cve.org/CVERecord?id=CVE

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-021135FasterXML, LLCのJackson-databindにおけるサーバサイドのリクエストフォージェリの脆弱性

jackson-databind は Jackson Data Processor の汎用データバインディング機能およびツリーモデルを含むライブラリです。バージョン 2.0.0 から 2.18.8、2.21.4、および 3.1.4 まで、JDKFromStringDeserializer は new InetSocketAddress(host, port) を使って InetSocketAddress を構築しており、これは逆シリアライズ時にホスト名入力に対して積極的な DNS 名前解決を行います。InetSocketAddress フィールドを含む型に信頼できない JSON をバインドするアプリケーションは、readValue の処理中に攻撃者が選択した DNS クエリを発行し、アプリケーションレベルの検証や接続ロジックの前にこれが発生します。この問題の修正は InetSocketAddress.createUnresolved(host, port) を使用し、DNS 解決を明示的な接続時まで遅延させる方法で行われました。この脆弱性は 2.18.8、2.21.4、および 3.1.4 で修正されています。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
04

Evidence and provenance

Published 23 Jun 2026 · Last source change 25 Jun 2026, 12:59 UTC · CWE-918 · Server-Side Request Forgery (SSRF)

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-38592
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-38592↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference · GitHub GHSA-HGJ6-7826-R7M5↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-54514 · cve.blacktree.nl