CVE Intelligence
Critical Insecure deserialization

CVE-2019-16943 — Deserialization of Untrusted Data in Debian Debian Linux

A Polymorphic Typing issue was discovered in FasterXML jackson-databind 2.0.0 through 2.9.10. When Default Typing is enabled (either globally or for a specific property) for an externally exposed JSON endpoint and the service has the p6spy (3.8.6) jar in the classpath, and an attacker can find an RMI service endpoint to access, it is possible to make the service execute a malicious payload. This issue exists because of com.p6spy.engine.spy.P6DataSource mishandling.

Published Oct 1, 2019 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: mitre

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 4.9% (30-day exploitation probability)+14
  • Technical severity (critical)+10
  • Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
4.9%
ahead of 92% of scored CVEs · Oct 14, 2026
Affects
Debian
Debian Linux and 25 more
CVSS base
9.8
Critical · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
Yes
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Documented patch — github.com (NIST National Vulnerability Database)
  • Documented patch — www.oracle.com (NIST National Vulnerability Database)
  • Documented patch — www.oracle.com (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Debian Debian Linux, Fasterxml Jackson-databind, Fedoraproject Fedora…).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. Apply the fixed version or the patch documented under Remediation.
  4. EPSS ahead of 92% of scored CVEs: prioritize it in the patch queue.
  5. Search available logs for exploit probes matching the vulnerability class (insecure deserialization), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Debian Debian Linux version 8.0version 9.0version 10.0 Vulnerable NIST National Vulnerability Database
Fasterxml Jackson-databind ≥ 2.0.0 and < 2.6.7.3≥ 2.7.0 and < 2.8.11.5≥ 2.9.0 and < 2.9.10.1 Vulnerable NIST National Vulnerability Database
Fedoraproject Fedora version 31version 30 Vulnerable NIST National Vulnerability Database
Netapp Active Iq Unified Manager ≥ 7.3≥ 9.5 Vulnerable NIST National Vulnerability Database
Netapp Oncommand Api Services versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp Oncommand Workflow Automation versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp Service Level Manager versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp Steelstore Cloud Integrated Storage versions not specified by the source Vulnerable NIST National Vulnerability Database
Oracle Banking Platform version 2.6.0version 2.6.1version 2.6.2version 2.7.0version 2.7.1version 2.9.0version 2.5.0version 2.4.1
and 1 more version 2.4.0
Vulnerable NIST National Vulnerability Database
Oracle Communications Billing And Revenue Management version 7.5.0.23.0version 12.0.0.3.0 Vulnerable NIST National Vulnerability Database
Oracle Communications Calendar Server version 8.0.0.3.0version 8.0.0.2.0 Vulnerable NIST National Vulnerability Database
Oracle Communications Cloud Native Core Network Slice Selection Function version 1.2.1 Vulnerable NIST National Vulnerability Database
Oracle Communications Evolved Communications Application Server version 7.1 Vulnerable NIST National Vulnerability Database
Oracle Global Lifecycle Management Nextgen Oui Framework version 12.2.1.4.0version 12.2.1.3.0version 13.9.4.2.2 Vulnerable NIST National Vulnerability Database
Oracle Goldengate Application Adapters version 19.1.0.0.0 Vulnerable NIST National Vulnerability Database
Oracle Jd Edwards Enterpriseone Orchestrator version 9.2 Vulnerable NIST National Vulnerability Database
Oracle Jd Edwards Enterpriseone Tools version 9.2 Vulnerable NIST National Vulnerability Database
Oracle Primavera Gateway version 16.2≥ 17.7 and ≤ 17.12.6≥ 18.8.0 and ≤ 18.8.8version 16.1version 19.12.0 Vulnerable NIST National Vulnerability Database
Oracle Retail Merchandising System version 16.0.3version 16.0.2version 15.0.3 Vulnerable NIST National Vulnerability Database
Oracle Retail Sales Audit version 14.1 Vulnerable NIST National Vulnerability Database
Oracle Siebel Engineering - Installer & Deployment ≤ 2.20.5 Vulnerable NIST National Vulnerability Database
Oracle Trace File Analyzer version 12.2.0.1version 18cversion 19c Vulnerable NIST National Vulnerability Database
Oracle WebCenter Portal version 12.2.1.4.0version 12.2.1.3.0 Vulnerable NIST National Vulnerability Database
Oracle Webcenter Sites version 12.2.1.4.0version 12.2.1.3.0 Vulnerable NIST National Vulnerability Database
Oracle Weblogic Server version 12.2.1.4.0version 12.2.1.3.0 Vulnerable NIST National Vulnerability Database
Red Hat Jboss Enterprise Application Platform version 7.3version 7.2 Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
9.8 CVSS 3.1 Critical 3.9 5.9 nvd@nist.gov via NIST National Vulnerability Database
9.8 CVSS 3.1 Critical 3.9 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database
9.8 CVSS 3.1 Critical — — CISA-ADP via CVE Program (cve.org) e CISA ADP
6.8 CVSS 2.0 Medium 8.6 6.4 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-502 · Deserialization of Untrusted Data

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 4.90%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Monitor serialized objects in requests and unexpected processes spawned by the runtime.
web/proxy/WAF logsnetwork IDS/IPSendpoint telemetry (EDR)application logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • Fix documented
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 9.8
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • 2019
  • CVE published
    Oct 1, 2019 · mitre

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

26 on the record

Elsewhere on this site

Debian
every CVE for this vendor
Insecure deserialization
same class
CWE-502
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-83038 Vulnerability in the Oracle WebLogic Server product of Oracle Fusion Middleware (component:... Sep 15, 2026
  • CVE-2026-12996 A use-after-free in OpenVPN 2.6.0 through 2.6.20 and 2.7_alpha1 through 2.7.4 allows remote... Jul 30, 2026
  • CVE-2026-54518 jackson-databind: @JsonView bypass for unwrapped creator parameters in jackson-databind Jun 23, 2026
  • CVE-2026-54512 jackson-databind: PolymorphicTypeValidator bypass via generic type parameters allows arbitrary class instantiation Jun 23, 2026
  • CVE-2026-54513 jackson-databind: Array subtype allowlist bypass in BasicPolymorphicTypeValidator (allowIfSubTypeIsArray) Jun 23, 2026
  • CVE-2026-54514 jackson-databind: InetSocketAddress deserialization triggers eager DNS resolution (SSRF) Jun 23, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2019-16943 is "Deserialization of Untrusted Data in Debian Debian Linux", rated Critical. It affects Debian Linux (Debian); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.8 describes technical severity. EPSS 4.90% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.