CVE-2026-1290VulnerabilityPublished 21 Jan 2026

CVE-2026-1290: Jamf Pro · Authentication Bypass by Primary Weakness

Affects Jamf ProSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: Low
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Subsequent System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
JamfJamf Pro	Affected >=11.20 <=11.24	Fixed in–

AI-suggested

1. Monitor Jamf’s official channels for patches addressing CVE-2026-1290 and apply them promptly once released. 2. Restrict network access to Jamf Pro management interfaces using firewalls, VPNs, or zero-trust network access solutions to limit exposure to trusted administrators only. 3. Implement strong network segmentation to isolate Jamf Pro servers from general user networks and the internet. 4. Enforce multi-factor authentication (MFA) on all administrative accounts, even if the vulnerability bypasses some authentication steps, to add an additional security layer. 5. Conduct regular audits of Jamf Pro access logs to detect unusual or unauthorized login attempts or configuration changes. 6. Review and minimize the number of users with administrative privileges in Jamf Pro to reduce the attack surface. 7. Employ endpoint detection and response (EDR) tools on managed devices to identify suspicious activities potentially resulting from compromised Jamf Pro access. 8. Educate IT staff about this vulnerability and ensure incident response plans include scenarios involving Jamf Pro compromise. 9. If immediate patching is not possible, consider temporarily disabling remote access to Jamf Pro consoles or placing them behind strict access controls. 10. Maintain up-to-date backups of Jamf Pro configurations and device management data to enable recovery in case of compromise.

Description

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

Impact

For European organizations, this vulnerability presents a risk of unauthorized access to Jamf Pro management consoles, potentially allowing attackers to manipulate device management policies, deploy malicious configurations, or access sensitive information about managed Apple devices. This could lead to broader compromise of endpoint security, data leakage, or disruption of device management operations. Organizations relying heavily on Apple ecosystems, such as those in education, healthcare, and government sectors, may face increased risk. The medium severity score reflects that while the vulnerability does not directly compromise system integrity or availability, the authentication bypass could serve as a stepping stone for further attacks. The lack of known exploits reduces immediate risk but does not eliminate the threat, especially as attackers often develop exploits post-disclosure. European entities with remote or internet-facing Jamf Pro consoles are particularly vulnerable. The impact is compounded in environments where Jamf Pro is integrated with other critical IT systems or where privileged credentials are reused. Failure to address this vulnerability could result in unauthorized administrative actions, compliance violations, and reputational damage.

CWE-305Authentication Bypass by Primary Weakness (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The authentication algorithm is sound, but the implemented mechanism can be bypassed as the result of a separate weakness that is primary to the authentication error.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
V9.2.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

learn.jamf.com/en-US/bundle/jamf-pro-release-notes-11.24.0/page/Resolved_Issues.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 21 Jan 2026, 15:50 UTC

WeaknessesCWE-305

Technical details

References

Community reviews

Related threats