{
  "format_version": 1,
  "canonical_url": "https://davidstrnadel.com/",
  "source_content_updated": "2026-11-02T12:00:00+00:00",
  "provenance": "Derived from the public portfolio HTML and public technical writeups. This is the author-maintained profile; linked vendor advisories are the external attribution sources.",
  "person": {
    "@context": "https://schema.org",
    "@type": "Person",
    "@id": "https://davidstrnadel.com/#person",
    "name": "David Strnadel",
    "givenName": "David",
    "familyName": "Strnadel",
    "url": "https://davidstrnadel.com/",
    "email": "security@davidstrnadel.com",
    "jobTitle": "Security Researcher",
    "description": "Security researcher from the Czech Republic, credited by Apple for three iOS and macOS vulnerabilities. Previously five years of automotive software testing at ZF Group.",
    "image": {
      "@type": "ImageObject",
      "@id": "https://davidstrnadel.com/#photo",
      "url": "https://davidstrnadel.com/photo/david-strnadel-800.jpg",
      "contentUrl": "https://davidstrnadel.com/photo/david-strnadel-800.jpg",
      "width": 800,
      "height": 1000,
      "caption": "David Strnadel"
    },
    "nationality": {
      "@type": "Country",
      "name": "Czech Republic"
    },
    "homeLocation": {
      "@type": "Country",
      "name": "Czech Republic"
    },
    "knowsLanguage": [
      "cs",
      "en"
    ],
    "alumniOf": {
      "@type": "CollegeOrUniversity",
      "name": "Tomas Bata University in Zlín",
      "sameAs": "https://www.utb.cz/en/"
    },
    "sameAs": [
      "https://github.com/o0SilentStorm0o",
      "https://www.linkedin.com/in/david-strnadel-714990245"
    ],
    "knowsAbout": [
      "Apple platform security",
      "iOS security",
      "macOS security",
      "Vulnerability research",
      "Reverse engineering",
      "Binary diffing",
      "Kernel security",
      "Automotive software testing",
      "AUTOSAR",
      "Machine learning"
    ]
  },
  "career_and_education": [
    {
      "period": "2026 — present",
      "organization_or_activity": "Independent security research",
      "details": "Apple platforms, reverse engineering, and AI-assisted vulnerability discovery.",
      "source_url": "https://davidstrnadel.com/#about"
    },
    {
      "period": "2026",
      "organization_or_activity": "Revelia",
      "details": "AI Analyst / Data Scientist / Project Manager.",
      "source_url": "https://davidstrnadel.com/#about"
    },
    {
      "period": "2021 — 2026",
      "organization_or_activity": "ZF Group",
      "details": "Software testing in embedded and AUTOSAR environments.",
      "source_url": "https://davidstrnadel.com/#about"
    },
    {
      "period": "Education",
      "organization_or_activity": "Tomas Bata University in Zlín",
      "details": "BSc in Software Engineering, 2025. MSc in Cybersecurity.",
      "source_url": "https://davidstrnadel.com/#about"
    }
  ],
  "public_cve_credits": [
    {
      "cve": "CVE-2026-65398",
      "component": "IOMobileFrameBuffer",
      "credit_and_impact_summary": "Out-of-bounds access · Shared credit",
      "source_url": "https://davidstrnadel.com/research/cve-2026-65398/",
      "text_url": "https://davidstrnadel.com/research/cve-2026-65398/index.md",
      "vendor_advisory_url": "https://support.apple.com/en-us/149034",
      "scope": [
        {
          "label": "Tested build",
          "value": "iOS 27 beta 4 · 24A5390f"
        },
        {
          "label": "Entry point",
          "value": "IOKit · selector 95"
        },
        {
          "label": "Evidence",
          "value": "Physical-device archive"
        },
        {
          "label": "Attribution",
          "value": "Shared Apple credit"
        }
      ],
      "evidence_notes": [
        "Scope of this article The addresses and offsets below belong to the recorded beta-4 build. Apple’s public advisory covers the CVE; it is not a claim that these exact layouts apply to every affected platform.",
        "A useful distinction A panic can prove which address a kernel instruction attempted to load. It does not, by itself, prove that the app received the contents of mapped kernel memory. The writeup keeps those two claims separate.",
        "Provenance Kernel-read witness executable SHA-256: 3c702ee05c472e0725bc5c4f170cc6f0848731a6de28b6213cd7ed82139dc906 Recorded component UUID: F96D5B5D-7440-3947-B481-F5AC2E379FF7 . This identifies the archived build; it is not a hash of the downloadable editorial excerpt."
      ],
      "impact_and_limits": "04 Impact & limits # What the evidence supports Ordinary-app reachability on the tested build. A missing index check and a native out-of-bounds operation. Full-width kernel register control in the original witness. A crash-based kernel-load demonstration satisfying the recorded Target-Flag read contract. What it does not establish Kernel data returned to the application as a general readback oracle. An arbitrary-write primitive. Program-counter control or kernel code execution. The exact beta-4 mechanism on every affected Apple platform. A useful distinction A panic can prove which address a kernel instruction attempted to load. It does not, by itself, prove that the app received the contents of mapped kernel memory. The writeup keeps those two claims separate. Apple’s public advisory describes an out-of-bounds access issue with potential system termination or kernel-memory corruption, addressed through improved bounds checking. Credit is shared with other researchers. [E3]"
    },
    {
      "cve": "CVE-2026-43664",
      "component": "Accessibility",
      "credit_and_impact_summary": "Sensitive user data · Shared credit",
      "source_url": "https://davidstrnadel.com/research/cve-2026-43664/",
      "text_url": "https://davidstrnadel.com/research/cve-2026-43664/index.md",
      "vendor_advisory_url": "https://support.apple.com/en-us/149034",
      "scope": [
        {
          "label": "Reported test build",
          "value": "iOS 26.4 · 23E246"
        },
        {
          "label": "Access path",
          "value": "CFPreferences / cfprefsd"
        },
        {
          "label": "Evidence",
          "value": "Original-report reconstruction"
        },
        {
          "label": "Attribution",
          "value": "Shared Apple credit"
        }
      ],
      "evidence_notes": [
        "Reading the evidence This technical note reconstructs the experimental logic from my original submission and disclosure record. The original local project and raw test archive have not been recovered for this edition. Observations below are attributed to that submission; they are not presented as a freshly reproduced test.",
        "Observation versus root-cause explanation The submission attributed the exposure to permissive preference policy. This edition has not independently revalidated that internal policy or Apple’s cross-build implementation. The access-path observation and Apple’s CVE outcome are presented separately.",
        "What would strengthen this edition A recovered original test project, exact queried domains and keys, and the app/widget evidence pairs would support a reproducible appendix. Until then, this article explicitly preserves the distinction between reported behaviour and independently rechecked artifacts."
      ],
      "impact_and_limits": "04 CVE-specific outcome # Apple describes the Accessibility issue as an app being able to access sensitive user data. This is the public impact associated with this CVE, rather than a claim that every preference or arbitrary file was exposed. [E2] What the evidence supports The access-path mismatch described in the original submission. A separate-process observation and a negative write-propagation control, as recorded in that submission. Public Apple acknowledgement of CVE-2026-43664. What it does not establish Arbitrary writes across preference domains. A general escape from all sandbox restrictions. An independently revalidated binary-level root cause in this edition. Exact affected keys or raw payloads absent from the available archive."
    },
    {
      "cve": "CVE-2026-43730",
      "component": "AuthKit",
      "credit_and_impact_summary": "Permissions issue · User fingerprinting",
      "source_url": "https://davidstrnadel.com/research/cve-2026-43730/",
      "text_url": "https://davidstrnadel.com/research/cve-2026-43730/index.md",
      "vendor_advisory_url": "https://support.apple.com/en-asia/128067",
      "scope": [
        {
          "label": "Reported test build",
          "value": "iOS 26.4 · 23E246"
        },
        {
          "label": "Access path",
          "value": "CFPreferences / cfprefsd"
        },
        {
          "label": "Evidence",
          "value": "Original-report reconstruction"
        },
        {
          "label": "Attribution",
          "value": "Apple credit"
        }
      ],
      "evidence_notes": [
        "Reading the evidence This technical note reconstructs the experimental logic from my original submission and disclosure record. The original local project and raw test archive have not been recovered for this edition. Observations below are attributed to that submission; they are not presented as a freshly reproduced test.",
        "Observation versus root-cause explanation The submission attributed the exposure to permissive preference policy. This edition has not independently revalidated that internal policy or Apple’s cross-build implementation. The access-path observation and Apple’s CVE outcome are presented separately.",
        "What would strengthen this edition A recovered original test project, exact queried domains and keys, and the app/widget evidence pairs would support a reproducible appendix. Until then, this article explicitly preserves the distinction between reported behaviour and independently rechecked artifacts."
      ],
      "impact_and_limits": "04 CVE-specific outcome # Apple describes the AuthKit issue as an app being able to fingerprint the user, and reports additional restrictions as the remediation. Fingerprinting here means identifying or correlating a user; it does not mean reading biometric fingerprints. [E2] What the evidence supports The access-path mismatch described in the original submission. A separate-process observation and a negative write-propagation control, as recorded in that submission. Public Apple acknowledgement of CVE-2026-43730. What it does not establish Arbitrary writes across preference domains. A general escape from all sandbox restrictions. An independently revalidated binary-level root cause in this edition. Exact affected keys or raw payloads absent from the available archive."
    }
  ],
  "selected_investigations": [
    {
      "title": "A forgotten safety check in the core of iOS",
      "summary": "A forgotten safety check in the core of iOS According to Apple, an app could use it to crash the device or corrupt kernel memory, the most protected part of the system. While comparing iOS builds, I noticed that a new operation in IOMobileFrameBuffer lacked a condition present in a related one. That difference became an out-of-bounds hypothesis, a proof of concept, and a report to Apple.",
      "details": "From difference to hypothesis I used binary diffing to narrow down security-relevant changes during the iOS beta cycle. Comparing related operations helped isolate a missing condition and formulate a testable out-of-bounds hypothesis. Test, then report I developed an on-device proof of concept and documented the result for Apple. I directed the investigation and used AI to accelerate reverse analysis, PoC development, and the technical report. Public outcome Apple credited the issue as CVE-2026-65398, with shared attribution. Its advisory describes an out-of-bounds access issue that could allow an app to cause a system crash or corrupt kernel memory.",
      "source_url": "https://davidstrnadel.com/#research"
    },
    {
      "title": "An app read data it should never have seen",
      "summary": "An app read data it should never have seen An app locked in its own sandbox could still read data from other parts of the system, including information that could help identify the user. The sandbox denied direct file reads, while public preference APIs in AuthKit and Accessibility returned data from other domains.",
      "details": "Compare the access paths I built an on-device proof of concept to compare denied direct file reads with service-mediated preference access. A separate WidgetKit extension provided an independent process for checking the behaviour. Rule out the wrong conclusion Cross-process controls helped distinguish data exposure from writes that remained in a process-local cache. Those writes did not establish a cross-process write capability. One investigation, two issues Apple split the original report and tracked the resulting issues under AuthKit (CVE-2026-43730) and Accessibility (CVE-2026-43664). The Accessibility credit is shared with other researchers.",
      "source_url": "https://davidstrnadel.com/#research"
    }
  ],
  "ai_research": [
    {
      "name": "VQE-in-GAN",
      "status": "Preprint · 2025",
      "description": [
        "Preprint · 2025",
        "Can a quantum-inspired idea help generative AI models train better?",
        "I explored VQE-inspired auxiliary losses in GAN training using PyTorch and Qiskit simulation. Controlled comparisons found no measurable benefit over simpler classical alternatives in the studied setting.",
        "Simulator-based study. Published methods, ablations, and a negative result."
      ],
      "references": [
        {
          "label": "Read the preprint ↗",
          "url": "https://arxiv.org/abs/2512.12581"
        },
        {
          "label": "Code ↗",
          "url": "https://github.com/o0SilentStorm0o/VQE-in-GAN"
        }
      ],
      "source_url": "https://davidstrnadel.com/#ai"
    },
    {
      "name": "JEPA × spiking networks",
      "status": "Ongoing · Master’s research",
      "description": [
        "Ongoing · Master’s research",
        "Could brain-inspired computing benefit from a modern way of learning?",
        "I investigate whether JEPA-style learning could benefit neuromorphic computation, comparing conventional and spiking neural networks through software experiments.",
        "PyTorch experiments and Lava simulation. No experiments on physical Intel Loihi hardware."
      ],
      "references": [
        {
          "label": "Code ↗",
          "url": "https://github.com/o0SilentStorm0o/jepa-substrate"
        }
      ],
      "source_url": "https://davidstrnadel.com/#ai"
    }
  ],
  "availability": "Building on Apple platforms, running a security team, or researching similar problems? I’m happy to talk about vulnerability research, reverse engineering and turning a hunch into reproducible evidence.",
  "contact_url": "mailto:security@davidstrnadel.com",
  "cv_url": "https://davidstrnadel.com/David-Strnadel-CV.pdf",
  "text_profile_url": "https://davidstrnadel.com/index.md",
  "research_index_url": "https://davidstrnadel.com/research/"
}
