Joaquim Grilo
04/08/2026, 1:39 PMkapa.ai
04/08/2026, 1:39 PMpackage.json / lockfile of the SDK version you use (or the GitHub repo) to see the exact Axios version and transitive dependencies.
2. Review the React SDK changelog and “What’s New” page for any security‑related notes not present in these excerpts. [React SDK changelog; What’s new]
3. If you need an official security statement, open a ticket with GoodData Support or your account representative, referencing the specific Axios CVE or incident you’re concerned about.
If you share the exact SDK version and Axios advisory (e.g., CVE ID), I can help you interpret what to look for in the changelog and dependency tree, but I can’t confirm any remediation steps beyond what’s in the linked docs. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups.
👀 Our Support team monitors all messages and will jump in if needed.Mauricio Cabezas
04/08/2026, 2:29 PMaxios@1.14.1 or axios@0.30.4).
There is a small chance that if you ran npm install during the brief window the compromised versions were live (~3 hours on March 31), npm could have resolved to one of them. To verify, run:
npm ls axios
If you see 1.14.1 or 0.30.4, we recommend reinstalling with the current clean version.
As a best practice going forward, we recommend always using a lockfile (package-lock.json or pnpm-lock.yaml) and verifying the resolved Axios version after installing or updating the GoodData SDK.
Let me know if you have any questions!Joaquim Grilo
04/08/2026, 4:11 PM