How severe is CVE-2017-10269?

CVE-2017-10269 has a CVSS 3.x base score of 10.0, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability low.

Is CVE-2017-10269 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (80th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2017-10269?

CVE-2017-10269 primarily affects Oracle Tuxedo. In total, 4 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2017-10269?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2017-10269 published?

CVE-2017-10269 was published on 2017-11-14 and last updated on 2026-06-17.

CVE-2017-10269

CVE-2017-10269 is a critical-severity vulnerability in Oracle Tuxedo with a CVSS 3.x base score of 10.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Critical (CVSS 3.x base score 10.0)
CVSS v2: 7.5
EPSS exploit prediction: 2% (80th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Oracle Tuxedo
Published: 2017-11-14
Last modified: 2026-06-17

Description

Vulnerability in the Oracle Tuxedo component of Oracle Fusion Middleware (subcomponent: Core). Supported versions that are affected are 11.1.1, 12.1.1, 12.1.3 and 12.2.2. Easily exploitable vulnerability allows unauthenticated attacker with network access via Jolt to compromise Oracle Tuxedo. While the vulnerability is in Oracle Tuxedo, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Tuxedo accessible data as well as unauthorized access to critical data or complete access to all Oracle Tuxedo accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Tuxedo. CVSS 3.0 Base Score 10.0 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L).

Frequently asked questions

What is CVE-2017-10269?: Vulnerability in the Oracle Tuxedo component of Oracle Fusion Middleware (subcomponent: Core). Supported versions that are affected are 11.1.1, 12.1.1, 12.1.3 and 12.2.2. Easily exploitable vulnerability allows unauthenticated attacker with network access via Jolt to compromise Oracle Tuxedo. While the vulnerability is in Oracle Tuxedo, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Tuxedo accessible data as well as unauthorized access to critical data or complete access to all Oracle Tuxedo accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Tuxedo. CVSS 3.0 Base Score 10.0 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L).
How severe is CVE-2017-10269?: CVE-2017-10269 has a CVSS 3.x base score of 10.0, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability low.
Is CVE-2017-10269 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (80th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2017-10269?: CVE-2017-10269 primarily affects Oracle Tuxedo. In total, 4 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2017-10269?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2017-10269 published?: CVE-2017-10269 was published on 2017-11-14 and last updated on 2026-06-17.

References

Affected products (4)

cpe:2.3:a:oracle:tuxedo:11.1.1:*:*:*:*:*:*:*
cpe:2.3:a:oracle:tuxedo:12.1.1:*:*:*:*:*:*:*
cpe:2.3:a:oracle:tuxedo:12.1.3:*:*:*:*:*:*:*
cpe:2.3:a:oracle:tuxedo:12.2.2:*:*:*:*:*:*:*

More vulnerabilities in Oracle Tuxedo

CVE-2017-10272 — Critical (CVSS 9.9): Vulnerability in the Oracle Tuxedo component of Oracle Fusion Middleware (subcomponent: Core). Supported versions that…
CVE-2022-23305 — Critical (CVSS 9.8): By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be…
CVE-2022-23307 — High (CVSS 8.8): CVE-2020-9493 identified a deserialization issue that was present in Apache Chainsaw. Prior to Chainsaw V2.0 Chainsaw…
CVE-2022-23302 — High (CVSS 8.8): JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write…
CVE-2018-3007 — High (CVSS 8.6): Vulnerability in the Oracle Tuxedo component of Oracle Fusion Middleware (subcomponent: Core). Supported versions that…
CVE-2021-4104 — High (CVSS 7.5): JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the…

All CVEs affecting Oracle Tuxedo →