1177 matches found
CVE-2026-90486 openstatusHQ openstatus resolve-custom-domain-rewrite.ts server-side request forgery
A vulnerability has been found in openstatusHQ openstatus up to f04c827112f30a11d571ebdad3892826034d6265. Affected by this vulnerability is an unknown functionality of the file apps/status-page/src/lib/proxy/resolve-custom-domain-rewrite.ts. The manipulation leads to server-side request forgery...
CVE-2026-90486 openstatusHQ openstatus resolve-custom-domain-rewrite.ts server-side request forgery
A vulnerability has been found in openstatusHQ openstatus up to f04c827112f30a11d571ebdad3892826034d6265. Affected by this vulnerability is an unknown functionality of the file apps/status-page/src/lib/proxy/resolve-custom-domain-rewrite.ts. The manipulation leads to server-side request forgery...
CVE-2026-90486
A vulnerability has been found in openstatusHQ openstatus up to f04c827112f30a11d571ebdad3892826034d6265. Affected by this vulnerability is an unknown functionality of the file apps/status-page/src/lib/proxy/resolve-custom-domain-rewrite.ts. The manipulation leads to server-side request forgery...
CVE-2026-90486: Server-Side Request Forgery (SSRF)
A vulnerability has been found in openstatusHQ openstatus up to f04c827112f30a11d571ebdad3892826034d6265. Affected by this vulnerability is an unknown functionality of the file apps/status-page/src/lib/proxy/resolve-custom-domain-rewrite.ts. The manipulation leads to server-side request forgery...
Malicious code in export-double-cache-benchmark-resolve (npm)
The package export-double-cache-benchmark-resolve was found to contain malicious code. --- Credit: OpenSSF source...
Malicious code in export-resolve-theta-slow-refactor (npm)
Source: amazon-inspector 38a82e294ea324bca472096d25a02a11bb79c13ed4c1729e7d4735c3cf05ccf2 This package appears to be part of the tea.xyz token reward campaign that flooded npm. These packages typically contain autopublish scripts auto.js, autopublish.js, autopublish2.js, autopublish3.js designed ...
Malicious code in error-float-report-resolve-sigma (npm)
The package error-float-report-resolve-sigma was found to contain malicious code. --- Credit: OpenSSF source...
Malicious code in emulate-tau-grep-resolve-decompress (npm)
Source: amazon-inspector 537111f2ce71d83f483cdf19d12bda80c8b9dbbb1a5081022d1fdbd029694e33 This package appears to be part of the tea.xyz token reward campaign that flooded npm. These packages typically contain autopublish scripts auto.js, autopublish.js, autopublish2.js, autopublish3.js designed ...
Malicious code in double-grid-resolve-data-log (npm)
Source: amazon-inspector ec84b8cf5799e8ac659af511e2e198a7e75ad80f432bb110d8f87a68bdef0b35 This package appears to be part of the tea.xyz token reward campaign that flooded npm. These packages typically contain autopublish scripts auto.js, autopublish.js, autopublish2.js, autopublish3.js designed ...
PYSEC-2026-4010 Arbitrary file read via workspace confinement bypass in local-operator /v1/chat/agents/{id}/edit
The /v1/chat/agents/agentid/edit endpoint in local-operator versions before 0.47.5 resolves the caller-supplied filepath with expanduser.resolve and reads it without checking that it lies inside the agent's workspace. An unauthenticated client with network access to the API can supply an absolute...
Malicious code in container-bundle-wind-private-resolve (npm)
Source: amazon-inspector 7db1e29795f86285de0d3050a91ae132752d5fe260eb95e9a4c113a4d16ed7da This package appears to be part of the tea.xyz token reward campaign that flooded npm. These packages typically contain autopublish scripts auto.js, autopublish.js, autopublish2.js, autopublish3.js designed ...
Malicious code in compile-catch-gamma-encode-resolve (npm)
Source: amazon-inspector 7b8545b272f2cc1d5247f5d8fc850fd0c53e182c3852a6ab567e2c4e0085d24b This package appears to be part of the tea.xyz token reward campaign that flooded npm. These packages typically contain autopublish scripts auto.js, autopublish.js, autopublish2.js, autopublish3.js designed ...
Malicious code in compile-dog-resolve-java-slow (npm)
The package compile-dog-resolve-java-slow was found to contain malicious code. --- Credit: OpenSSF source...
Malicious code in cluster-sanitize-resolve-omega-encrypt (npm)
Source: amazon-inspector bcceef72f7076040ad3f53d861981ebd1e83dc7bf7e6c4bbd7c584c0c40e5a6e This package appears to be part of the tea.xyz token reward campaign that flooded npm. These packages typically contain autopublish scripts auto.js, autopublish.js, autopublish2.js, autopublish3.js designed ...
Malicious code in cluster-protected-resolve-cloud-refactor (npm)
Source: amazon-inspector 16bf76a6aad62a8326f2acada064db0631acce7a0d63f70078133976b476da61 This package appears to be part of the tea.xyz token reward campaign that flooded npm. These packages typically contain autopublish scripts auto.js, autopublish.js, autopublish2.js, autopublish3.js designed ...
Malicious code in cloud-object-new-resolve-grid (npm)
The package cloud-object-new-resolve-grid was found to contain malicious code. --- Credit: OpenSSF source...
Malicious code in bash-water-resolve-unix-error (npm)
Source: amazon-inspector 8aa208583cc81c4598465e3b44b85048c1d4a747fe9087200fc8eabae365d5fb This package appears to be part of the tea.xyz token reward campaign that flooded npm. These packages typically contain autopublish scripts auto.js, autopublish.js, autopublish2.js, autopublish3.js designed ...
Malicious code in balance-rho-resolve-alpha-uglify (npm)
The package balance-rho-resolve-alpha-uglify was found to contain malicious code. --- Credit: OpenSSF source...
Malicious code in bad-key-short-sudo-resolve (npm)
Source: amazon-inspector d95126115936cadcb064f8ebc6d168464fb327bc7d45149cd0e410f044d9352b This package appears to be part of the tea.xyz token reward campaign that flooded npm. These packages typically contain autopublish scripts auto.js, autopublish.js, autopublish2.js, autopublish3.js designed ...
PT-2026-82970
Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description An out-of-bounds heap read exists in the machine resolve function. The issue occurs because the function accesses env-cpual-cpu.socket id without validating the al-cpu variable against...