LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1290: [PI141230] Fixed A broken access control issue.

Authentication Bypass by Primary Weakness vulnerability in Jamf Jamf Pro allows unspecified impact.This issue affects Jamf Pro: from 11.20 through 11.24.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-1290 is a Jamf Pro broken access control issue described as authentication bypass with unspecified impact. It affects Jamf Pro 11.20 through 11.24 according to the CVE data. Severity is medium, not because it is harmless, but because disclosed impact is limited and details are sparse.

Executive priority

Prioritize this as a near-term patch and exposure review for Jamf Pro environments. Business risk is concentrated in device-management systems, where access-control failures can have outsized operational impact. Current public evidence does not justify emergency exploitation response absent additional indicators.

Technical view

The record maps to CWE-305 and CVSS 4.0 score 5.3. The vector indicates network access, low attack complexity, low privileges required, no user interaction, and limited confidentiality impact across vulnerable and subsequent systems. Public sources do not describe the bypass path, affected endpoints, or data exposed.

Likely exposure

Organizations running Jamf Pro versions 11.20 through 11.24 should treat those instances as potentially exposed, especially internet-accessible or broadly reachable management portals. Default status is listed as unaffected outside the named range, but administrators should confirm against Jamf guidance.

Exploitation context

The source bundle does not show CISA KEV listing or any cited evidence of active exploitation. Exploitability is plausibly reachable over the network with low privileges, but the public record does not provide operational details or confirmed exploitation.

Researcher notes

Public disclosure is thin. The CVE states authentication bypass by primary weakness and unspecified impact, while the Jamf reference is a resolved-issues page. Affected range and fixed-version interpretation should be validated directly with Jamf documentation before making remediation claims.

Mitigation direction

  • Identify all Jamf Pro deployments and their exact versions.
  • Review Jamf release notes for PI141230 and CVE-2026-1290.
  • Upgrade or apply Jamf-recommended fixes once the correct fixed version is confirmed.
  • Restrict network access to Jamf Pro administration interfaces where feasible.
  • Monitor vendor advisories for clarification on affected and fixed versions.

Validation and detection

  • Confirm whether any Jamf Pro instance runs 11.20 through 11.24.
  • Check vulnerability scanner results against the CVE identifier.
  • Compare installed version against Jamf’s resolved-issues documentation.
  • Review access-control related logs for unusual authenticated activity.
  • Document compensating controls for externally reachable Jamf Pro systems.
Prepared
Confidence
medium
Sources
3

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.

cwe · low confidence lookup

CWE-305: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-1290 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
Medium
CVSS
5.3 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N

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
2Source 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
5.3CVSS 4.0MediumCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

5.3Medium
CVSS 4.0 vector shape for CVE-2026-1290Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
JamfJamf Pro11.20unaffected
Weakness

CWE details

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

CWE-305 · source CWE mapping

Authentication Bypass by Primary Weakness

Authentication Bypass by Primary Weakness represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.