ZeroDay Findings
Sign inSign up

Every 4 hours

Cyber

Keywords match titles. Record type separates incidents, intel, and research from CVEs.

  1. Research · Aug 20, 2025 · ZeroDay Catalog

    Critical Out-of-Bounds Write Vulnerability in Apple Operating Systems

    Apple has addressed a significant out-of-bounds write vulnerability affecting multiple operating systems, which may have been exploited in targeted attacks.

    What changed

    Apple has resolved an out-of-bounds write vulnerability that could lead to memory corruption when processing malicious image files. This issue has been fixed in several recent updates across its operating systems.

    The vulnerability was addressed with enhanced bounds checking, significantly improving the security posture of affected systems.

    Who is affected

    Users of Apple’s iOS, iPadOS, and macOS are at risk, particularly those who have not yet updated to the latest versions.

    The vulnerability impacts a wide range of devices, including iPhones, iPads, and Mac computers.

    • Apple iOS versions 15.8.5, 16.7.12, and 18.6.2
    • Apple iPadOS versions 15.8.5, 16.7.12, and 17.7.10
    • macOS Sequoia 15.6.1, Sonoma 14.7.8, and Ventura 13.7.8
    • Specific targeted individuals may have been affected by sophisticated attacks leveraging this vulnerability.

    What to do

    It is crucial for users and organizations to promptly update their devices to the latest versions of iOS, iPadOS, and macOS to mitigate the risk associated with this vulnerability.

    Regularly monitoring security advisories from Apple and implementing best practices for device security can further reduce exposure.

    • Update to the latest iOS, iPadOS, and macOS versions immediately.
    • Monitor for any unusual activity that may indicate exploitation.
    • Educate users about the risks of processing unknown or suspicious files.

    Original report

  2. Research · Jul 25, 2025 · ZeroDay Catalog

    Critical Command Injection Vulnerability in tj-actions/branch-names

    A critical command injection vulnerability has been discovered in the tj-actions/branch-names GitHub Action, posing significant risks to downstream workflows.

    What changed

    A severe command injection vulnerability has been identified in the tj-actions/branch-names GitHub Action. This flaw allows for arbitrary command execution in downstream workflows due to inconsistent input sanitization and unescaped output.

    Malicious actors can exploit this vulnerability by crafting specific branch names or tags, leading to potential unauthorized command execution.

    Who is affected

    Organizations utilizing the tj-actions/branch-names GitHub Action are at risk of this vulnerability. The impact is particularly significant for those relying on automated workflows that process branch names or tags.

    Developers and teams using GitHub Actions for CI/CD pipelines should be aware of this issue to mitigate risks.

    • GitHub Action users employing tj-actions/branch-names.
    • Organizations with automated workflows that handle branch names.
    • Development teams integrating GitHub Actions into their CI/CD processes.

    What to do

    It is crucial for affected users to review their workflows and implement necessary changes to mitigate the risks associated with this vulnerability. Immediate actions should include updating the tj-actions/branch-names to the latest version where the vulnerability is addressed.

    Additionally, consider implementing stricter input validation and output sanitization in your workflows to prevent potential exploitation.

    • Update tj-actions/branch-names to the latest secure version.
    • Review and enhance input validation mechanisms in workflows.
    • Monitor for any unusual activity in workflows that may indicate exploitation attempts.

    Original report