Vigilbase CVEConnect your agent

Apple Multiple Products Improper Authentication Vulnerability

Known exploitedExploited · KEV 2026-11-04Trending #7CVE-2024-27834CWE-287

Exploited since 2026-11-04. No WAF vendor names it yet.

Edge rules
0/9
Our test
No exploit yet
CVSS
8.1
EPSS
1.4% Top 27%
Posts, 14d
1662026-10-24: 0 posts2026-10-25: 0 posts2026-10-26: 0 posts2026-10-27: 0 posts2026-10-28: 0 posts2026-10-29: 0 posts2026-10-30: 0 posts2026-10-31: 0 posts2026-11-01: 0 posts2026-11-02: 0 posts2026-11-03: 0 posts2026-11-04: 41 posts2026-11-05: 108 posts2026-11-06: 17 posts
Published
2024-05-13

What it is

The issue was addressed with improved checks. This issue is fixed in Safari 17.5, iOS 16.7.8 and iPadOS 16.7.8, iOS 17.5 and iPadOS 17.5, macOS Sonoma 14.5, tvOS 17.5, watchOS 10.5. An attacker with arbitrary read and write capability may be able to bypass Pointer Authentication.

From the CVE record · CVE-2024-27834 ↗
Known exploitedLast checked 2026-11-06

The risk

CISA lists CVE-2024-27834 as exploited in the wild since 2026-11-04. No edge WAF vendor names it in a changelog, so default managed rules may or may not catch it.

Who is affected

Teams running Apple Safari (before 17.5), Apple iOS and iPadOS (before 16.7.8; before 17.5) and Apple macOS (before 14.5).

Next steps

  1. Find the version you run. In Terminal:
    sw_vers
  2. Apply the vendor's fix; the advisory lists the affected and fixed versions. support.apple.com ↗
  3. CISA's required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. US federal agencies must act by 2026-11-18.
  4. Review exposed instances for signs of compromise: it was exploited before many systems were patched, and a later patch does not undo access already gained.
  5. Do not rely on WAF defaults: no edge vendor names this CVE. Restrict access to the vulnerable component or add a custom rule until it is patched. Edge coverage
  6. Check which WAF sits in front of your site and whether it covers this CVE. Check your domain

Exploitation activity

Last 90 days
Honeypot days
0 / 90
Last attempt seen
—
Listed exploited
4 Nov CISA
Telegram claims
1 days, unverified

Attack traffic on Cloudflare

Cloudflare Radar
  • Broken Authentication16% of mitigated layer 7 attacks, 7 days2026-10-09: 5.1%2026-10-10: 4.3%2026-10-11: 5.2%2026-10-12: 5%2026-10-13: 6%2026-10-14: 5.4%2026-10-15: 6.6%2026-10-16: 5.8%2026-10-17: 5.2%2026-10-18: 4.2%2026-10-19: 5%2026-10-20: 4.2%2026-10-21: 3.2%2026-10-22: 4.5%2026-10-23: 6.3%2026-10-24: 4.4%2026-10-25: 3.9%2026-10-26: 4.5%2026-10-27: 6.5%2026-10-28: 5.9%2026-10-29: 6.5%2026-10-30: 16.3%2026-10-31: 13.4%2026-11-01: 18.1%2026-11-02: 17%2026-11-03: 14%2026-11-04: 16.7%2026-11-05: 16.8%2026-11-06: 14%
  • Rules for named CVEs5.7% of mitigated layer 7 attacks, 7 days2026-10-09: 6.3%2026-10-10: 1.9%2026-10-11: 0.8%2026-10-12: 0.6%2026-10-13: 0.6%2026-10-14: 4.2%2026-10-15: 2.3%2026-10-16: 1.3%2026-10-17: 1.6%2026-10-18: 1.1%2026-10-19: 3.2%2026-10-20: 4.7%2026-10-21: 5.7%2026-10-22: 5.5%2026-10-23: 9.8%2026-10-24: 7%2026-10-25: 5%2026-10-26: 7.3%2026-10-27: 8.1%2026-10-28: 10.1%2026-10-29: 0.9%2026-10-30: 4.1%2026-10-31: 7.5%2026-11-01: 8.7%2026-11-02: 2.4%2026-11-03: 7.5%2026-11-04: 7.3%2026-11-05: 3.9%2026-11-06: 1.4%

Radar groups Cloudflare's WAF managed rules by category; it does not publish counts per CVE. These shares show how much attack traffic targets this kind of flaw across Cloudflare's network (28-day trend). They are not compromised systems, and seeing few attempts on Cloudflare does not prove an absence elsewhere. Radar data as of 2026-11-06. Radar ↗

Check your exposure with an agent

Read-only

Copy this into an agent with access to your infrastructure. It asks for an evidence-based, read-only assessment: affected systems, exposure, compensating controls and what is still unknown. It does not scan or change anything by itself.

Prompt12 lines
Assess whether the infrastructure available to you is affected by CVE-2024-27834 (Apple Multiple Products Improper Authentication Vulnerability). Perform a read-only assessment within your authorized access. Do not send exploit traffic, scan third-party systems, change configuration or restart services.

1. Verify the CVE record at https://www.cve.org/CVERecord?id=CVE-2024-27834 and the vendor advisory. Establish affected and fixed versions, including vendor backports. The record lists: Apple Safari: affected before 17.5 | Apple iOS and iPadOS: affected before 16.7.8; before 17.5 | Apple macOS: affected before 14.5. Cite sources and retrieval dates; flag anything you cannot verify.
2. Inventory deployments of Apple Multiple Products: asset, environment, owner where known, installed version or build, and how you confirmed it (package metadata, a version endpoint, image tags), e.g. `sw_vers` (in Terminal). An image tag alone does not prove the running version.
3. Identify which deployments are reachable from the internet or untrusted networks, and through which paths (direct origin, load balancer, CDN or WAF).
4. Assess compensating controls separately from patch status. Current edge WAF coverage for this CVE: no edge WAF vendor names it. Live data: https://cve.vigilbase.com/api/v1/cves/CVE-2024-27834. Check whether the rule is enabled and in block mode on each path, and whether any path bypasses the WAF. A WAF rule is not a patch.
5. It is known exploited (CISA KEV): review logs on exposed instances for signs of exploitation before and after patching.

Return a short summary and a table: asset | version/build | assessment (affected, fixed, not applicable, unknown) | exposure | compensating control | evidence | next action. List what you could not assess and the access needed to resolve it. Do not infer absence of compromise from patch status or a lack of alerts.

Remediation guidance: Apply the vendor's fix; the advisory lists the affected and fixed versions. CISA's required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. US federal agencies must act by 2026-11-18.
More: https://cve.vigilbase.com/cve/CVE-2024-27834

Sources

Cited
CVE record

CVSS 3.1 8.1 (high). Weakness: CWE-287.

CVE-2024-27834 ↗NVD ↗

Vendor advisory

Fixes and mitigations the CVE record links to. Check affected builds against the vendor, including backports.

support.apple.com ↗support.apple.com ↗support.apple.com ↗support.apple.com ↗

Exploit evidence

No public exploit code found in Exploit-DB, Metasploit, nuclei-templates or GitHub. That does not mean none exists.

Seen exploited

Listed in an independent exploited-vulnerability catalog on 4 Nov 2026. Claimed in 2 Telegram posts (unverified).

CISA KEV

Added 2026-11-04, federal due date 2026-11-18 (catalog 2026.11.04, checked 2026-11-06).

CISA KEV catalog ↗

EPSS

1.41% probability of exploitation activity in the next 30 days, higher than 72% of CVEs (2026-11-05).

FIRST EPSS ↗

WAF vendor statements

No edge vendor changelog names it.

Ask Vigil

AI · answers from this page
Ask about CVE-2024-27834: who's covered, what to patch first, how vendors compare. I cite sources and won't help with attacks.

Severity, decoded

CVSS 3.1
High · 8.1 / 10

Exploitable with local access under specific conditions, with no privileges and no user interaction, leading to full loss of confidentiality, integrity and availability, and the impact can reach components beyond the vulnerable one.

Needs local accessNo login neededNo user actionHard to pull offSpreads beyond the appFull compromise
How the score is built8 metrics
  • Attack vectorAn attacker needs local access, or must trick a user into opening something on the machine.
    Local
  • Attack complexityThe attack only works when conditions outside the attacker's control line up.
    High
  • Privileges requiredNo account or login is needed.
    None
  • User interactionNo one has to click or open anything; the attack works on its own.
    None
  • ScopeThe attack can spread beyond the vulnerable component to other parts of the system.
    Changed
  • Confidentiality impactAn attacker can read all data the affected component holds, or the most sensitive parts of it.
    High
  • Integrity impactAn attacker can change any data or files the affected component protects.
    High
  • Availability impactAn attacker can take the component down completely or keep it from serving anyone.
    High
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
CISA's assessmentSSVC, from the CVE record
ExploitationNone

CISA has seen no public exploit and no attacks.

AutomatableYes

Attackers can script the attack end to end and hit many targets at once.

Technical impactTotal

A successful attack gives full control over the affected software or all of its data.

Public exploits

None found
0 Metasploit0 Exploit-DB0 Scanner template0 GitHub PoCs

No exploit in Exploit-DB or Metasploit, and no scanner template. That lowers, but doesn't remove, the chance of mass exploitation.

Timeline

  1. 2024-05-13
    CVE published
    CVE List
  2. 2026-11-04
    Added to CISA KEV
    Confirmed exploitation in the wild
  3. 2026-11-04
    First social mention we saw

Social

2026-10-24: 0 posts2026-10-25: 0 posts2026-10-26: 0 posts2026-10-27: 0 posts2026-10-28: 0 posts2026-10-29: 0 posts2026-10-30: 0 posts2026-10-31: 0 posts2026-11-01: 0 posts2026-11-02: 0 posts2026-11-03: 0 posts2026-11-04: 41 posts2026-11-05: 108 posts2026-11-06: 17 posts

Top posts

  • Mike Kipruto@itsMikeKipruto·

    Hackers are exploiting an Apple vulnerability patched in May 2024. CISA has added CVE-2024-27834 to its Known Exploited Vulnerabilities catalog. The attacks, attributed to Russia-linked APT29, reportedly use compromised websites and malicious JavaScript to bypass Apple's

    ♥ 4View on X
  • xploitdigest_kev@xploitdigest_kev@infosec.exchange·

    Do you run Apple Multiple Products? CISA lists CVE-2024-27834 as exploited (added 4 Nov 2026). Can it reach you? Only with access to the machine itself. It needs a user account, and nobody has to click. CVSS 5.5. Plain-English breakdown: https:// xploitdigest.com/kev/CVE-2024- 2…

    ♥ 2View on Mastodon
  • overflo.ws@overflo_ws@infosec.exchange·

    Added to CISA's Known Exploited Vulnerabilities catalog: CVE-2024-27834 Apple Multiple Products Improper Authentication Vulnerability CVSS 5.5 (Medium). EPSS 0.6%. US federal agencies must remediate by 2026-11-18. Apple iOS, iPadOS, macOS, Safari, tvOS and watchOS 10.5 contain a…

    ♥ 2View on Mastodon
  • CISA Cyber@CISACyber·

    🛡️We added improper authentication vulnerability CVE-2024-27834 affecting multiple Apple products to our Known Exploited Vulnerabilities Catalog. Visit https://t.co/myxOwap1Tf & apply mitigations to protect your org. #Cybersecurity #InfoSec https://t.co/IggJtpxDt6

    ♥ 2View on X
  • AX-NEWS CVE watch@axnews@infosec.exchange·

    🛡️ The CVEs that mattered · Thursday 5 November 1. CVE-2023-20198 · Critical 10.0 · exploited — Cisco IOS XE Web UI 2. CVE-2024-27834 · Medium 5.5 · exploited — Apple Multiple Products 3. CVE-2026-83844 · High 8.1 — Microsoft Paint https:// ax-news.com/cve # CVE # infosec

    ♥ 1View on Mastodon
  • Yazoul - Cybersecurity Alerts@Matchbook3469@infosec.exchange·

    🔵 THREAT INTELLIGENCE Hackers Exploit Patched Apple Flaw to Deliver Info-Stealing Malware, CISA Says Vulnerability | CRITICAL CVEs: CVE-2024-27834 The U.S. Cybersecurity and Infrastructure Security Agency (CISA) on Wednesday added a medium-severity security flaw impacting multi…

    ♥ 1View on Mastodon

Vendor statements

Quoted
CloudflareWAF Managed RulesBefore feed history

The CVE predates the oldest entry in this vendor's public feed, so a rule may exist that we cannot see.

AWSAWS WAF Managed RulesNo public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. AWS often describes a vulnerability without naming its CVE (for example "Log4j"). We count only entries that name the CVE, so AWS coverage is understated.

Microsoft AzureFront Door and Application Gateway WAF (DRS)No public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. The rule tables name CVEs but carry no dates, so Azure is left out of every time-to-rule figure.

Google CloudCloud Armor preconfigured WAF rulesBefore feed history

The CVE predates the oldest entry in this vendor's public feed, so a rule may exist that we cannot see.

FastlyNext-Gen WAF virtual patchesBefore feed history

The CVE predates the oldest entry in this vendor's public feed, so a rule may exist that we cannot see.

VercelVercel WAF (platform rules)Before feed history

The CVE predates the oldest entry in this vendor's public feed, so a rule may exist that we cannot see.

F5Attack signatures (Distributed Cloud WAF)No public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. Each signature lists the CVEs it references, with its id and date. F5 does not state a default action; signatures enforce once staging ends in your policy.

AkamaiApp & API Protector (Adaptive Security Engine)No public source

This vendor publishes no machine-readable rule changelog we can check.

OWASP CRSCore Rule Set (open source, used inside many WAFs)No public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. CRS rarely names CVEs: it relies on generic detections. Our own lab measures what it actually blocks.