Security readout for executives and security teams
Plain-English summary
Time4Popcorn’s update components may let an unauthenticated remote attacker run arbitrary code, potentially compromising affected devices and their data. The record rates this critical at CVSS 9.8. However, the supplied evidence contains inconsistencies, so organizations should treat the risk urgently while confirming details with authoritative vendor guidance.
Executive priority
Prioritize immediate inventory and containment because the claimed impact is complete device compromise without authentication. Avoid assuming a patch exists: none is named in the supplied sources. Where Time4Popcorn is unnecessary, removal from organizational devices is the clearest risk-reduction option pending verified vendor information.
Technical view
CVE-2026-30612 describes remote code execution involving updater.exe on Windows and PT.updd on macOS. Listed limits are Windows 6.2.1.18, macOS 6.2.1.17, and Android 3.5.0.173. It is classified as CWE-494 with network access, low complexity, no privileges, and no user interaction. The Android attack path is not explained.
Likely exposure
Exposure is likely limited to devices running the listed Time4Popcorn versions or earlier. Windows and macOS updater components are specifically implicated. Android is listed as affected, but the supplied description does not identify its vulnerable component or attack path. No CPEs or reliable vendor identifier are provided.
Exploitation context
The supplied bundle says this can be exploited remotely without privileges or user interaction. It does not establish active exploitation, and the CVE is not identified as being in KEV. The included GitHub reference appears unrelated to Time4Popcorn, weakening corroboration of the technical claim.
Researcher notes
Confidence is limited by record-quality issues: affected vendor and product fields are “n/a,” no CPEs are supplied, and the sole third-party reference concerns an LB-Link router rather than Time4Popcorn. The Android mechanism and any fixed versions are unspecified. Validate against subsequent CVE updates and authoritative vendor material before making definitive technical claims.
Mitigation direction
- Inventory Time4Popcorn installations and compare versions against the stated affected limits.
- Check authoritative vendor guidance for corrected releases or supported mitigation.
- Until guidance is confirmed, consider removing affected software from business-critical devices.
- Restrict affected applications and updater components from unnecessary network access.
- Monitor affected endpoints for unexpected processes, persistence, or outbound connections.
Validation and detection
- Confirm installed Time4Popcorn versions across Windows, macOS, and Android devices.
- Verify whether updater.exe or PT.updd exists on relevant endpoints.
- Review vendor guidance before treating any newer version as fixed.
- Check endpoint telemetry for anomalous activity associated with the updater components.
- Reassess when the CVE record gains corrected product identifiers or relevant references.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-494: 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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-30612 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/Orcust-Automaton/Vulnerability/blob/main/LB-Link/AC1900_AZ2/bs_SetLimitCli_info.mdCVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Download of Code Without Integrity Check
Download of Code Without Integrity Check represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.