CVE-2025-43343: Input Validation
Published Sep 15, 2025
·Updated
AirPort. A permissions issue was addressed with additional restrictions.
Credit
Joey Hewitt, an anonymous researcher, Thomas Salomon, Sufiyan Gouri (TU Darmstadt), Phil Scott & Richard Hyunho Im (@richeeta)@@MrPeriPeri, Mark Bowers, Dylan Rollins, Arthur Baudoin, Andr.Ess, Jaydev Ahire, Big Bear, Pawel Wylecial(REDTEAM), Csaba Fitzl@@theevilbit(Kandji), Yinyi Wu@@_3ndy1(Dawn Security Lab of JD), @@zlluny(Trend Micro Zero Day Initiative), 이동하 (Lee Dong Ha)(SSA Lab), Keisuke Hosoda, Viktor Oreshkin, Mickey Jin@@patch1t, Dawuge(Shuffle Team), Noah Gregory (wts.dev), CVE-2025-6965, JZ, Seo Hyun-gyu@@wh1te4ever, Luke Roberts@@rookuu, Ignacio Sanmillan@@ulexec, Mike Cardwell(grepular), Bob Lord, Michael Reeves@@IntegralPilot, Hossein Lotfi@@hosselot(Trend Micro Zero Day Initiative), @@RenwaX23, Evan Waelde, Nikita Sakalouski, Rosyna Keller(Totally Not Malicious Software), Guilherme Rambo(Best Buddy Apps), Philipp Baldauf, Minghao Lin@@Y1nKoc, Lyutoon@@Lyutoon_, YingQi Shi@@Mas0n, Tom Brzezinski, Abhay Kailasia@@abhay_kailasia(C), KPC(Cisco Talos), 정답이 아닌 해답, Richard Hyunho Im@@richeeta, Zhongquan Li@@Guluisacat, Bilal Siddiqui, Nolan Astrein(Kandji), Shantanu Thakur, Wang Yu(Cyberserval), Anonymous(Trend Micro Zero Day Initiative), Yiğit Can YILMAZ@@yilmazcanyigit, Ye Zhang@@VAR10CK(Baidu Security), Nathaniel Oh@@calysteon, Gergely Kalman@@gergely_kalman, Hikerell (Loadshine Lab), Rodolphe Brunetti@@eisw0lf(Lupus Nova), Kirin@@Pwnrin, LFY@@secsys(Fudan University), CVE-2025-40909, Zhongcheng Li(IES Red Team of ByteDance), @@zlluny, CVE-2024-27280, Ye Zhang(Baidu Security), pattern-f@@pattern_F_, Kirin@@Pwnrin(Computer Science), Cristian Dinca(Computer Science), Romania, Ferdous Saljooki@@malwarezoo(Jamf), Justin Elliot Fu, Pyrophoria(GrapheneOS), an anonymous researcher(GrapheneOS), James J Kalafus, Michel Migdal, ken super, ABC Research s.r.o., Mickey Jin@@patch1t(Cisco Talos), Kirin@@Pwnrin(Cisco Talos), Claudio Bozzato(Cisco Talos), Francesco Benvenuto(Cisco Talos), Rodolphe BRUNETTI@@eisw0lf(Lupus Nova)
Affected Software
18 affected componentsFixes available
Apple iOS<26
26
Apple iPadOS<26
26
Apple WatchOS<26
26
Apple visionOS<26
26
Apple Safari<26
26
Apple tvOS<26
26
Apple macOS Tahoe<26
26
Apple Safari<26.0
Apple iPadOS<26.0
Apple iPhone OS<26.0
Apple macOS<26.0
Apple tvOS<26.0
Apple visionOS<26.0
Apple WatchOS<26.0
WebKitGTK WebKitGTK<2.50.1
wpewebkit WPE WebKit<2.50.1
debian/webkit2gtk<=2.44.2-1~deb11u1
2.50.6-1~deb11u12.50.4-1~deb12u12.50.6-1~deb12u12.50.4-1~deb13u12.52.3-2~deb13u12.52.3-2
debian/wpewebkit<=2.38.6-1~deb11u1, <=2.38.6-1, <=2.48.3-1
2.52.3-1
Event History
Sep 15, 2025
Data Sourced
via Apple·12:00 AM
DescriptionWeaknessAffected Software
Updated
via Apple·12:00 AM
DescriptionWeaknessAffected Software
Updated
via Apple·12:00 AM
DescriptionWeakness
CVE Published
via MITRE·10:35 PM
Data Sourced
via MITRE·10:35 PM
DescriptionWeakness
Data Sourced
via NVD·11:15 PM
DescriptionSeverityWeaknessAffected Software
Oct 13, 2025
Data Sourced
via Red Hat·08:02 PM
DescriptionSeverityAffected Software
Apr 6, 2026
Data Sourced
via Launchpad·05:50 PM
Description
Apr 9, 2026
Data Sourced
via Ubuntu·05:51 PM
RemedyDescriptionSeverityAffected Software
Apr 28, 2026
Data Sourced
via Debian·06:03 PM
DescriptionAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2025-43343?
CVE-2025-43343 has been rated with a high severity due to the potential for unauthorized access and buffer overflow risks.
2
How do I fix CVE-2025-43343?
To fix CVE-2025-43343, you should update to the latest version of macOS Tahoe, iOS, iPadOS, tvOS, watchOS, or visionOS as specified in the vendor's advisory.
3
What types of devices are affected by CVE-2025-43343?
CVE-2025-43343 affects Apple devices running macOS Tahoe, iOS, iPadOS, tvOS, watchOS, and visionOS up to version 26.
4
What specific issue does CVE-2025-43343 address?
CVE-2025-43343 addresses a permissions issue, a buffer overflow vulnerability, and an out-of-bounds access issue across various Apple operating systems.
5
Is there a workaround for CVE-2025-43343?
No official workaround is available; updating to the latest software version is necessary to mitigate the risks associated with CVE-2025-43343.