Security context
What an agent needs to avoid regressing past fixes and find the next vuln in this repo.
tensorflow/tfjs
master @ 7f5309f
9
Fixes
0
CVEs
HIGH
Peak severity
Highlights
Denial of Service: 9 prior fixes. Scrutinize any change in this area.
tfjs-node/binding/tfjs_backend.cc: most-fixed (2 issues). Treat as high-risk during review.
1 high-severity fix in this history; regressions here are high-impact.
Recurring patterns
The bug types that recur here, drawn from past fixes, not open vulnerabilities.
Denial of Service: Native memory leaks via unreleased tstring handles and string pointers during saved model loading/execution cause progressive memory-exhaustion. Developers must ensure C++ bindings explicitly free underlying resources when handles are destroyed.
Denial of Service: Dereferencing uninitialized or null native TensorHandle objects in TF_Tensor calls triggers immediate application crashes. Robust NULL pointer validations must be enforced at the boundary of all JS-to-C++ tensor wrappers.
Denial of Service: Large input arrays processed via JS spread-operator arguments (e.g. within StringSplit) can exceed maximum call-stack limits, leading to immediate process termination. Iterative or in-place array mutation must replace the spread operator for untrusted inputs.