LiveActive security incident?Get immediate response
CVE Record

CVE-2019-4266: IBM Maximo Anywhere 7.6.2.0, 7.6.2.1, 7.6.3.0, and 7.6.3.1 does not have device jailbreak detection which c...

IBM Maximo Anywhere 7.6.2.0, 7.6.2.1, 7.6.3.0, and 7.6.3.1 does not have device jailbreak detection which could result in an attacker gaining sensitive information about the device. IBM X-Force ID: 160199.

LowCVSS 2.4Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2019-4266 is a low-severity IBM Maximo Anywhere mobile security weakness. Affected versions lack jailbreak detection, so use on a compromised physical device could expose sensitive device information. The supplied sources do not show active exploitation.

Executive priority

Treat as low priority unless affected Maximo Anywhere is used on mobile devices carrying sensitive operational data. Address during the next mobile application maintenance cycle, with faster action for unmanaged device environments.

Technical view

IBM Maximo Anywhere 7.6.2.0, 7.6.2.1, 7.6.3.0, and 7.6.3.1 do not detect jailbroken devices. CVSS 3.0 score is 2.4 with physical attack vector, low confidentiality impact, and no integrity or availability impact.

Likely exposure

Exposure is limited to organizations using the listed IBM Maximo Anywhere versions on mobile devices, especially unmanaged or jailbroken devices. No other affected products are identified in the supplied sources.

Exploitation context

The CVSS vector indicates physical access is required and only device information confidentiality is affected. The CVE is not listed as KEV, and the supplied sources do not cite public exploitation.

Researcher notes

Evidence is concise: IBM describes missing jailbreak detection and potential device information exposure. No CWE is supplied. The CVSS vector shows physical access, low confidentiality impact, and official remediation availability, but the provided bundle does not name a specific fixed version.

Mitigation direction

  • Identify whether any listed Maximo Anywhere versions are still deployed.
  • Review IBM support guidance for the official remediation path.
  • Apply IBM’s official fix or upgrade guidance where applicable.
  • Enforce MDM controls that block jailbroken or rooted devices.
  • Restrict Maximo Anywhere access to managed, compliant devices.

Validation and detection

  • Confirm installed Maximo Anywhere versions against the affected version list.
  • Check MDM or device compliance reports for jailbreak status enforcement.
  • Verify IBM advisory remediation has been applied where required.
  • Review mobile access logs for use from non-compliant devices.
  • Document residual risk if affected versions remain in service.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2019-4266 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
2.4 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/A:N/I:N/AV:P/AC:L/S:U/C:L/PR:N/UI:N/RL:O/E:U/RC:C

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
2.4CVSS 3.0LowCVSS:3.0/A:N/I:N/AV:P/AC:L/S:U/C:L/PR:N/UI:N/RL:O/E:U/RC:C0.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

2.4Low
CVSS 3.0 vector shape for CVE-2019-4266Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/A:N/I:N/AV:P/AC:L/S:U/C:L/PR:N/UI:N/RL:O/E:U/RC:C

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
IBMMaximo Anywhere7.6.2.0, 7.6.2.1, 7.6.3.0, 7.6.3.1Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.