CVE Intelligence
Low Info disclosure

CVE-2020-10698 — A flaw was found in Ansible Tower when running jobs. This flaw allows an attacker to access the...

A flaw was found in Ansible Tower when running jobs. This flaw allows an attacker to access the stdout of the executed jobs which are run from other organizations. Some sensible data can be disclosed. However, critical data should not be disclosed, as it should be protected by the no_log flag when debugging is enabled. This flaw affects Ansible Tower versions before 3.6.4, Ansible Tower versions before 3.5.6 and Ansible Tower versions before 3.4.6.

Published May 27, 2021 · Updated Oct 24, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: redhat

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 0.3% (30-day exploitation probability)+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
0.27%
ahead of 19% of scored CVEs · Oct 27, 2026
Affects
Red Hat
Ansible Tower
CVSS base
3.3
Low · 2 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original 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 (Red Hat Ansible Tower).
  2. Apply the fixed version or the patch documented under Remediation.
  3. Search available logs for exploit probes matching the vulnerability class (info disclosure), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Red Hat Ansible Tower < 3.4.6≥ 3.5.0 and < 3.5.6≥ 3.6.0 and < 3.6.4 Vulnerable NIST National Vulnerability Database

Attack characteristics

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

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

Every base score collected

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

ScoreVersionSeverityExpl.ImpactScored by
3.3 CVSS 3.1 Low 1.8 1.4 nvd@nist.gov via NIST National Vulnerability Database
3.3 CVSS 3.1 Low — — GitHub, Inc. via GitHub Security Advisories
2.1 CVSS 2.0 Low 3.9 2.9 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-200 · Exposure of Sensitive Information

Other CVEs with this weakness →

EPSS over time FIRST

Oct 24, 2026 → Oct 27, 2026 · 4 reading(s) · max 0.27%

Detection

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

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
  • Look for anomalous data read/export volumes and access to sensitive records.
endpoint telemetry (EDR)application logsauthentication logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Record published
    Oct 24, 2026
  • Fix documented
    Oct 24, 2026 · NIST National Vulnerability Database
  • Affected products added · redhat/ansible tower
    Oct 24, 2026 · NIST National Vulnerability Database
  • CVSS changed · 3.3
    Oct 24, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 24, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 24, 2026 · Alertas do Telegram
  • 2021
  • CVE published
    May 27, 2021 · redhat

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 24, 2026 – Oct 24, 2026
  • 1× Official description updated · Oct 24, 2026 – Oct 24, 2026

References

3 on the record

Elsewhere on this site

Red Hat
every CVE for this vendor
Info disclosure
same class
CWE-200
other pages naming this weakness

Related CVEs (same products)

  • CVE-2018-1061 python before versions 2.7.15, 3.4.9, 3.5.6rc1, 3.6.5rc1 and 3.7.0 is vulnerable to catastrophic... Jun 19, 2018
  • CVE-2018-1060 Improper Input Validation in Python Jun 18, 2018
  • CVE-2018-0495 Libgcrypt before 1.7.10 and 1.8.x before 1.8.3 allows a memory-cache side-channel attack on ECDSA... Jun 13, 2018

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 CISA SSVC assessment.
  • 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-2020-10698 is "A flaw was found in Ansible Tower when running jobs. This flaw allows an attacker to access the...", rated Low. It affects Ansible Tower (Red Hat); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 3.3 describes technical severity. EPSS 0.27% 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.