Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, node-forge accepted a PKCS#12 MAC or PKCS#12 password-based encryption iteration count of zero or less. pki.pbe.generatePkcs12Key() then returned a constant key independent of the password and salt, allowing crafted PKCS#12 input processed by forge.pkcs12.pkcs12FromAsn1() to bypass password-based integrity checks. Predictable encryption keys and IVs also affected PKCS#12 PBE using pbeWithSHAAnd3-KeyTripleDES-CBC or pbewithSHAAnd40BitRC2-CBC, including shrouded key bags, encrypted SafeContents, and PKCS#8 ENCRYPTED PRIVATE KEY input processed independently by forge.pki.decryptPrivateKeyInfo(). PBES2/PBKDF2-encrypted content is unaffected. This issue is fixed in version 1.4.1.
ServiceNow has addressed a domain separation bypass security issue that was identified in the ServiceNow SR – CSM – Task Plan Templates Store application. This vulnerability could enable an authenticated user with a specific role to create records in domains they do not have access to, potentially leading to unauthorized data creation across domain boundaries.
We are not currently aware of malicious exploitation against ServiceNow instances. We recommend customers promptly apply appropriate updates or upgrade to a patched release if they have not already done so.
Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, the affected implementation used BigInteger.prototype.modInverse(), bnModInverse(), lib/jsbn.js, RSA public exponent e to process the relevant input or security decision. node-forge's bundled jsbn implementation entered an infinite loop when BigInteger.prototype.modInverse() received a negative value or modulus. An attacker who could control the RSA public exponent passed to key generation, or a direct modInverse() operand, could block the Node.js event loop at full CPU. Parsed DER, PEM, JWK, PKCS#12, X.509, and TLS values are unsigned and cannot trigger this issue. This issue is fixed in version 1.4.1.
Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, the affected implementation used pki.verifyCertificateChain(), pki.createCaStore(), duplicate subject names to process the relevant input or security decision. node-forge modified the CA store while trying certificates that shared a subject name during pki.verifyCertificateChain(). A failed chain verification could permanently remove trusted CA certificates from the store, causing later valid chains to fail and creating a persistent availability impact for applications that reused the store. This issue is fixed in version 1.4.1.
Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, the affected implementation used pem.decode(), lib/pem.js, missing END line to process the relevant input or security decision. node-forge used polynomial-time regular expressions in pem.decode(), including when searching for a matching END line and parsing encapsulated headers. An unauthenticated attacker able to supply PEM input to any high-level parser could consume excessive CPU with a long malformed message and cause denial of service. This issue is fixed in version 1.4.1.
Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, the affected implementation used forge.tls.createConnection(), c.session.serverCertificate, RSA key exchange to process the relevant input or security decision. node-forge's TLS client checked the wrong property when deciding whether a server certificate was missing. A malicious TLS server or on-path peer could omit the Certificate message and reach code that dereferenced the absent certificate, causing an uncaught exception and terminating the connection or process. This issue is fixed in version 1.4.1.
Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, the forge.http client stored cookie names and paths from Set-Cookie response headers in ordinary JavaScript objects. A malicious server could use the cookie name __proto__ so that the attacker-controlled cookie path was written as a property on Object.prototype, or use inherited names such as constructor to modify Object. An empty cookie value could use the removal path to delete an inherited Object.prototype property. Applications using forge.http directly or through forge.xhr are affected; applications that do not use forge.http are unaffected. This issue is fixed in version 1.4.1.
CVE-2026-103094 is an information disclosure vulnerability in the ServiceNow AI Platform where a user's plaintext OAuth credentials could be stored in a system table. This unintended persistence could expose sensitive passwords to unauthorized users. ServiceNow has released security updates in multiple patches across their Zurich, Yokohama, Xanadu, and Australia releases to remediate this issue. No known exploitation in the wild has been reported. Users are advised to apply the provided patches promptly.
A vulnerability in digitalbazaar's forge library (prior to version 1.4.1) involves improper input validation of PKCS#7 padding during CBC and ECB mode decryption. The library only validated the final byte of padding and accepted malformed padding, which could lead to silent removal of up to four plaintext blocks. This causes an integrity failure in applications relying on successful decryption as proof of valid padding. The issue is fixed in version 1.4.1.
CVE-2026-118775 is an integer overflow vulnerability in the digitalbazaar forge library prior to version 1.4.1. The flaw exists in the asn1.oidToDer() function, which did not properly range-check the first two arcs of an Object Identifier (OID). This could allow an application that accepts and authorizes an untrusted OID string to encode a DER representation that differs from the authorized OID. The vulnerability is fixed in version 1.4.1.
A cryptographic signature verification flaw exists in digitalbazaar's forge library versions prior to 1.4.1. The vulnerability involves improper verification of the signature scheme, where the library incorrectly uses the issuer certificate's RSA padding and RSASSA-PSS parameters instead of those from the child certificate. This could allow a child certificate labeled as RSASSA-PSS to be accepted with a PKCS#1 v1.5 signature if the issuer uses PKCS#1 v1.5. The flaw does not allow certificate identity forgery but may bypass policies enforcing specific signature schemes. The issue is resolved in version 1.4.1.
SuperAGI versions up to 0.0.14 have an improper access control vulnerability in the agent controller endpoint /api/agents/get/project/{project_id}. This flaw allows authenticated users from one organization to access the full list of agents belonging to projects of other organizations, due to lack of verification that the project_id belongs to the user's organization. The issue is fixed in version 0.0.15.
SuperAGI version 0.0.14 has an improper access control vulnerability in the get_agent_by_latest_execution function. This flaw allows a remote authenticated attacker from one organization to access the latest execution and agent metadata of another organization's project by providing the victim's project ID via a specific API endpoint.
TransformerOptimus SuperAGI version 0.0.14 has an incorrect access control vulnerability in the get_agent_execution_configuration function. This flaw allows a remote authenticated attacker from one organization to access another organization's agent execution configuration by providing specific agent and execution IDs. The affected endpoint does not verify organization ownership, leading to unauthorized data exposure.
OpenBMB XAgent version 1.0.0 contains a directory traversal vulnerability in the main-upload_file function located in ToolServer/ToolServerNode/main.py at line 46. This vulnerability could allow an attacker to access files outside the intended directory structure.
DB-GPT versions 0.7.5 and 0.8.0 contain a directory traversal vulnerability in the use_example_file function. This flaw allows a remote attacker to write files outside the intended workspace or storage boundary by exploiting the path validation. No patch or remediation information is provided.
HashiCorp Nomad and Nomad Enterprise contain a vulnerability allowing authenticated users with read permissions in one namespace to bypass authorization controls and view information in other namespaces via several read-only API endpoints. This issue is identified as CVE-2026-102260 and has a medium severity rating. The vulnerability is fixed in Nomad Community Edition 2.1.0 and Nomad Enterprise versions 2.1.0, 1.11.12, and 1.10.18.
HashiCorp Nomad and Nomad Enterprise contain a vulnerability involving symlink following during dispatch payload and executor log writes. This flaw allows a malicious workload to modify files outside its allocated directory. If the Nomad client agent runs with root privileges, exploitation could lead to root code execution on the client host. The vulnerability is tracked as CVE-2026-107347 and has a high severity rating with a CVSS score of 8.4. Fixed versions include Nomad 2.1.0 and Nomad Enterprise 2.1.0, 1.11.12, and 1.10.18.
The socket.getaddrinfo() function previously accepted null bytes within the host and port parameters, which could cause these values to be silently truncated. This behavior may lead to unexpected processing of network addresses.
modelscope agent-zero versions 1.7, 1.8, 1.9, and 1.10 contain a directory traversal vulnerability in the save_text_file method of python/helpers/file_browser.py. This method improperly handles user-supplied file paths without normalization or validation, allowing attackers to write files outside the intended directory.