CVE-2025-30432: A logic issue was addressed with improved state management.
Noroxi assessment
Priority: Monitor (action score 25/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.84% (FIRST EPSS); higher than 58.2% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A logic issue was addressed with improved state management. This issue is fixed in iOS 18.4 and iPadOS 18.4, iPadOS 17.7.6, macOS Sonoma 14.7.5, macOS Ventura 13.7.5, tvOS 18.4, visionOS 2.4, watchOS 11.4. A malicious app may be able to attempt passcode entries on a locked device and thereby cause escalating time delays after 4 failures.
- Published
- Mar 31, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.8% · 58th percentile
- CWE
- CWE-287
Report tools
Action score
25
Monitor
Low priority for now.
- CVSS
- 25 / 40 · 6.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.8%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| apple | ipados | cpe:2.3:o:apple:ipados |
| apple | iphone os | cpe:2.3:o:apple:iphone_os |
| apple | macos | cpe:2.3:o:apple:macos |
| apple | tvos | cpe:2.3:o:apple:tvos |
| apple | visionos | cpe:2.3:o:apple:visionos |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- apple ipadosbefore 17.7.6
- apple ipados18.0 and later · before 18.4
- apple iphone osbefore 18.4
- apple macos13.0 and later · before 13.7.5
- apple macos14.0 and later · before 14.7.5
- apple tvosbefore 18.4
- apple visionosbefore 2.4
Versions reported by the vendor
Affected version ranges reported by the assigning authority (apple). Independent of NVD's CPE analysis and usually ahead of it.
Apple iOS and iPadOS
- before 18.4affected
Apple iPadOS
- before 17.7.6affected
Apple macOS
- before 13.7.5affected
- before 14.7.5affected
Apple tvOS
- before 18.4affected
Apple visionOS
- before 2.4affected
Apple watchOS
- before 11.4affected
Same product
apple: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-43300An out-of-bounds write issue was addressed with improved bounds checking.KEV90Now
- CVE-2021-30860An integer overflow was addressed with improved input validation.KEV84Now
- CVE-2023-41064A buffer overflow issue was addressed with improved memory handling.KEV77This week
Published before and after this one in the same product
- ← EarlierCVE-2025-30429Mar 31, 2025 · A path handling issue was addressed with improved validation.25Monitor
- ← EarlierCVE-2025-30430Mar 31, 2025 · This issue was addressed through improved state management.39Monitor
- Later →CVE-2025-30433Mar 31, 2025 · This issue was addressed with improved access restrictions.39Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-304300 days apartThis issue was addressed through improved state management.39Monitor
- CVE-2026-84606532 days apartA privacy issue was addressed with improved handling of identifiers.30Monitor
- CVE-2026-84623532 days apartAn authorization issue was addressed with improved state management.30Monitor
- CVE-2026-20683532 days apartAn authentication issue was addressed with improved state management.28Monitor
- CVE-2025-3122842 days apartThe issue was addressed with improved authentication.27Monitor
- CVE-2024-23219434 days apartThe issue was addressed with improved authentication.24Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
- CVE-2024-4077175 days apartThe issue was addressed with improved memory handling.31Monitor
- CVE-2023-4296111 days apartA path handling issue was addressed with improved validation.25Monitor
- CVE-2024-5453575 days apartA path handling issue was addressed with improved logic.17Monitor
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- low · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- low · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- High
- Availability impact
- Low
Weakness class (CWE)
CWE-287 · Improper AuthenticationCVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:L
nvd-secondary
Root cause
Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.
The bug in code
The whole CWE-287 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use("/admin", requireSession, adminRouter);
// Route added later skips the middleware
app.post("/admin-api/config", updateConfig);Fixed
const admin = express.Router();
admin.use(requireSession, requireRole("admin"));
admin.post("/config", updateConfig);
app.use("/admin", admin);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Authentication AbuseCAPEC-114Medium
- Authentication BypassCAPEC-115Medium
- Identity SpoofingCAPEC-151likelihood: Medium · Medium
- Fake the Source of DataCAPEC-194Medium
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- Utilizing REST's Trust in the System Resource to Obtain Sensitive DataCAPEC-57likelihood: Medium · Very High
- Session HijackingCAPEC-593likelihood: High · Very High
- Token ImpersonationCAPEC-633Medium
ATT&CK techniques
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (13 more)Show less
- support.apple.com/en-us/122372
- support.apple.com/en-us/122374
- support.apple.com/en-us/122375
- support.apple.com/en-us/122376
- support.apple.com/en-us/122377
- support.apple.com/en-us/122378
- seclists.org/fulldisclosure/2025/Apr/10
- seclists.org/fulldisclosure/2025/Apr/11
- seclists.org/fulldisclosure/2025/Apr/12
- seclists.org/fulldisclosure/2025/Apr/13
- seclists.org/fulldisclosure/2025/Apr/4
- seclists.org/fulldisclosure/2025/Apr/5
- seclists.org/fulldisclosure/2025/Apr/9
Vendor advisories and official records. Exploit/PoC links are deliberately left out.