Latest articles

Application security blog

CVE explainers, code review patterns and practical guidance for people who build and own software.

  1. Practical guides

    Lovable and Supabase security checklist: what to check before launch

    Seven pre-launch checks for an AI-built app that keeps its data in Supabase, from Row Level Security and policies to keys, views, storage, the two-account test and account settings, drawn from Supabase, Lovable and OWASP documentation.

    Read article
  2. Practical guides

    How much does a web application pentest cost, and what is included?

    What drives the price of a web application and API pentest: roles, features, API methods and environments. What the work covers, what you receive, what is scoped separately and how to prepare your request.

    Read article
  3. Practical guides

    How to start in penetration testing, step by step

    A practical path for anyone who wants to become a web penetration tester: HTTP basics, Burp Suite, PortSwigger labs, OWASP and bug bounty, using free resources and a readiness check for every stage.

    Read article
  4. CVE explainers

    The Asterisk Paradox: CVE-2026-123158 and the OpenSSH–musl Authentication Bypass

    Two unrelated systems both chose the character "*" to mean "nothing usable here." CVE-2026-123158 traces exactly how that collision bypasses OpenSSH password authentication on musl-based Linux, what a pinned-digest lab run did and did not confirm, and the one question it left open.

    Read article
  5. Security news

    CVE-2026-118527: The Ivanti CVE CISA's Own Catalog Can't Explain

    CISA added CVE-2026-111357 and CVE-2026-118527 to the KEV catalog two weeks after CVE-2026-104935. One closes a gap from the original piece. The other raises a question nobody has answered yet.

    Read article
  6. CVE explainers

    CVE-2026-97229: the asterisk on GitLab’s ‘unauthenticated’ RCE

    GitLab’s CVSS 10.0 and CISA’s KEV call this unauthenticated. The only two people who made it work needed a GitLab account first. Here’s why that matters.

    Read article
  7. CVE explainers

    CVE-2026-98432: one function swapped for another, twice, and why disabling MPTCP isn’t the fix

    The kernel’s own fix for CVE-2026-98432 changed kfree() to kfree_rcu() in two destructors. Here’s why that one-word swap matters more than MPTCP does.

    Read article
  8. Security news

    PHP2Shell: CVE-2026-109618 and the Runtime Boundary

    PHP2Shell technical analysis: CVE-2026-109618, proposed memory-corruption stages, PHP version evidence, configuration dependencies, and fix verification.

    Read article
  9. Practical guides

    GhostAction: deleting a secret is not revoking it

    GhostAction mines old secrets. Separate rotation from Git history cleanup, then verify that exposed credentials and the workflow injection path are closed.

    Read article
  10. CVE explainers

    LMCache CVE-2026-105192: execution before rejection

    LMCache CVE-2026-105192 reaches pickle during message decoding. Follow the patch, transport callers and evidence needed to trust a negative regression test.

    Read article
  11. Practical guides

    ConnectWise Cloud Backup: the app never needed MFA

    The ConnectWise Cloud Backup incident exposes gaps between user MFA, app consent and token revocation. Learn what evidence actually establishes containment.

    Read article
  12. Practical guides

    Install AI coding tools without trusting a package name

    Install AI coding tools from a verified source. Check publisher identity, artifact integrity and execution access before sharing repositories or credentials.

    Read article
  13. CVE explainers

    CVE-2026-104935: Ivanti trusts the header, not the URL

    CVE-2026-104935 chains a routing header and an upload race into code execution on Ivanti Connect Secure. Full root needs a third, still-unpatched bug.

    Read article
  14. CVE explainers

    fast-jwt algorithm confusion: fixed on the third try

    fast-jwt has patched RSA to HS256 algorithm confusion three times. CVE-2026-107722 shows why the first two fixes closed an input instead of the rule.

    Read article
  15. CVE explainers

    CVE-2026-85097: Bricksforge trusts the file you name

    CVE-2026-85097 lets an anonymous visitor plant a PHP shell through a Bricksforge form. Here's the trust split behind it, and how to check your own uploads.

    Read article
  16. CVE explainers

    CVE-2026-21589: Atlassian’s file read that hides behind ::

    CVE-2026-21589 is an unauthenticated file read in eight Atlassian Data Center products. Here is the ordering bug behind it, and how to check your own code.

    Read article
  17. Security news

    Axios npm compromise: how the trust chain broke

    The Axios npm compromise wasn’t a code bug. Follow the six links of the trust chain, the control that breaks each one, and what npm 12 changes.

    Read article
  18. CVE explainers

    After React2Shell: three security boundaries every server component review needs

    A technical review method for React2Shell and CVE-2026-23864: separate safe decoding, permission checks and bounded work, then verify the deployed build.

    Read article
  19. Security news

    The 2026 Axios attack: why a clean dependency tree cannot clear a build runner

    An evidence-led analysis of the Axios supply-chain compromise: trace package installation, code execution and credential reach before declaring recovery complete.

    Read article
  20. CVE explainers

    CVE-2024-26855: when a missing attribute becomes a NULL dereference

    A Linux ice driver fix illustrates a common review mistake: treating a parser’s optional result as a guaranteed object.

    Read article
  21. CVE explainers

    CVE-2025-37858: a 64-bit destination cannot fix a narrow shift

    A JFS allocation-group calculation demonstrates why code review must inspect the width of an operation before its result is assigned.

    Read article
  22. Practical guides

    Security code review or penetration testing: what should you buy?

    Choose the engagement from the question your product team needs answered, the access available and the change you need to make.

    Read article

08Contact

Shipping something that handles user data?

Send me a short brief. I reply within three days with questions or a proposal outline, and the price is agreed in writing before work starts.