CVE-2025-10703 — Code Injection in Progress DataDirect Connect for JDBC Autonomous REST Connector

Triage

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

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.

Remediation

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

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

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 (Progress DataDirect Connect for JDBC Autonomous REST Connector, Progress DataDirect Connect for JDBC for Amazon Redshift, Progress DataDirect Connect for JDBC for Apache Cassandra…).
2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
3. Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Attack characteristics

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

Every base score collected

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

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-94 · Code Injection

Other CVEs with this weakness →

EPSS over time FIRST

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

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).
• Look for parameters with command/query metacharacters and unexpected child processes of the service.

Timeline

What happened to this CVE, newest first.

• 2026
• Affected products added · progress/datadirect connect for jdbc for amazon redshift, progress/datadirect connect for jdbc for apache cassandra, pro
  Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
• SSVC assessment updated
  Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
• Record published
  Oct 13, 2026
• CVSS changed · 8.6
  Oct 13, 2026 · NIST National Vulnerability Database
• Source status changed · → Deferred
  Oct 13, 2026 · NIST National Vulnerability Database
• Record created in this database
  Oct 13, 2026 · NIST National Vulnerability Database
• 2025
• CVE published
  Nov 19, 2025 · ProgressSoftware

Source activity

Repeated readings are counted rather than listed.

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

References

1 on the record

• community.progress.com/s/article/Progress-DataDirect-Critical-Security-Product-Alert-Bulleti
  NIST National Vulnerability Database

Elsewhere on this site

Related CVEs (same products)

• High CVE-2025-10702 Code Injection in Progress DataDirect Connect for JDBC for Amazon Redshift Nov 19, 2025

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 fixed version, patch or mitigation documented.
• 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-2025-10703 is "Code Injection in Progress DataDirect Connect for JDBC Autonomous REST Connector", rated High. It affects DataDirect Connect for JDBC Autonomous REST Connector (Progress); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.6 describes technical severity. EPSS 0.30% 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.