Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

npm package

better-call

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 4.9npmAmendedPublished

    Better Call routing bug can lead to Cache Deception

    GHSA-hq75-xg7r-rx6c

    Affected
    • npm better-call < 1.0.12
    Fixed in
    1.0.12· Vendor fix available
    Issue
    Using a CDN that caches (//.png, //.json, //.css, etc...) requests, a cache deception can emerge. This could lead to unauthorized access to user sessions and personal data when cached responses are served to other users. Details The vulnerability occurs in the request processing logic where path sanitization is insufficient. The library splits the path using config.basePath but doesn't properly validate the remaining path components. This allows specially crafted requests that appear to be static assets (like /api/auth/get-session/api/auth/image.png assuming config.basePath=/api/auth) to bypass typical CDN cache exclusion rules while actually returning sensitive data. The problematic code here: Since this library is largely coupled with better-auth, it becomes more clear why this can be dangerous with an example request: <img width="800" alt="image" src="https://github.com/user-attachments/assets/2ab7c4dd-0700-4f59-863f-79f2b5edbb37" / Impact This is a cache deception…

    Recommended action: Upgrade to 1.0.12 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →