PULSE
FEED
ransomiah6477 reclama a alera · Professional Servicesransomn0n reclama a Company #68 · US · Not Foundransomn0n reclama a Company #67 · NL · Not Foundransomn0n reclama a Company #66 · Not Foundransomn0n reclama a Interior Technologies · Technologyransomeclipse reclama a Taiwan Otsuka Pharmaceutical · TW · Healthcareransomeclipse reclama a japantimes.co.jp · JP · Otherransomakira reclama a FOODMatch · Agriculture and Food Productionransomakira reclama a Shediac Lobster Shop · CA · Retail & E-Commerceransomakira reclama a Torns Enterprises · Not Foundransomkairos reclama a Oceania Digital Communications · VU · Technologyransomincransom reclama a FINANCIAMENTO LTDA · BR · Financial Servicesransomqilin reclama a MOA Architecture · SG · Professional Servicesransomqilin reclama a Joliet Public Schools District 86 · US · Educationransomiah6477 reclama a alera · Professional Servicesransomn0n reclama a Company #68 · US · Not Foundransomn0n reclama a Company #67 · NL · Not Foundransomn0n reclama a Company #66 · Not Foundransomn0n reclama a Interior Technologies · Technologyransomeclipse reclama a Taiwan Otsuka Pharmaceutical · TW · Healthcareransomeclipse reclama a japantimes.co.jp · JP · Otherransomakira reclama a FOODMatch · Agriculture and Food Productionransomakira reclama a Shediac Lobster Shop · CA · Retail & E-Commerceransomakira reclama a Torns Enterprises · Not Foundransomkairos reclama a Oceania Digital Communications · VU · Technologyransomincransom reclama a FINANCIAMENTO LTDA · BR · Financial Servicesransomqilin reclama a MOA Architecture · SG · Professional Servicesransomqilin reclama a Joliet Public Schools District 86 · US · Education
← Todos los CVEs
CVE Watch14 oct 2026

CVE-2026-106172

A use of hard-coded cryptographic key vulnerability in Fortinet FortiSandbox 5.2.0 through 5.2.1, FortiSandbox 5.0.0 through 5.0.6, FortiSan

CVSS

5.3

Medio

EPSS

0.2%

p14

KEV

—

Exploit Today

4

0-100

Publicado: 13 oct 2026 · Última mod.: 14 oct 2026 · CWE-321

EPSS · 30d

Sin historial EPSS suficiente todavía.

Descripción técnica

A use of hard-coded cryptographic key vulnerability in Fortinet FortiSandbox 5.2.0 through 5.2.1, FortiSandbox 5.0.0 through 5.0.6, FortiSandbox 4.4 all versions, FortiSandbox Cloud 5.2.0 through 5.2.1, FortiSandbox Cloud 5.0.0 through 5.0.6, FortiSandbox Cloud 4.4 all versions may allow attacker to escalation of privilege via specially crafted HTTP requests

Referencias oficiales
CVEs relacionados
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2026-108336—
—
——0When the default self-signed certificate is used, an attacker could gain administrative access to the application. The SSL certificate for the web interface is used to sign JWT access tokens that are used to validate that the user is logged in. When the default SSL certificate is used, an attacker could have the capability to sign JWT access tokens and bypass login. An attacker could gain administrative access to the application and perform actions like configuring the service or requesting log collection. Device credentials and customer data cannot be accessed with this vulnerability.11h
CVE-2026-100413—
—
——0SeaweedFS is a distributed storage system for files and blobs. From 4.0.388 until 4.41, the SFTP Helm chart embedded one unencrypted Ed25519 private host key in k8s/charts/seaweedfs/templates/sftp/sftp-secret.yaml as stringData.seaweedfs_sftp_ssh_private_key. A standalone deployment presented that public key when sftp.enabled and sftp.enableAuth were true, sftp.existingConfigSecret was not supplied, the legacy sftp.sshPrivateKey path remained selected, a valid config-ssh Secret allowed startup, and hostKeysFolder did not provide a later Ed25519 signer. An attacker able to redirect or intercept client traffic could impersonate that SFTP endpoint to clients that trusted the published host identity, exposing password credentials or data sent to the rogue endpoint. Default all-in-one and non-authenticated standalone paths did not load the key. This issue is fixed in version 4.41.15h
CVE-2026-1106129.8 CRÍ
—
——0vlife through 2.0.1 contains an authentication bypass vulnerability that allows unauthenticated attackers to forge JWTs using the hardcoded HS256 signing key in TokenUtil. Attackers can sign a token with superUser=true and arbitrary groupIds claims to gain super administrator access to any URL on vlife instances.15h
CVE-2026-107171—
1.8%
——1An Hardcoded Cryptographic Key vulnerability existed in Trellix Agent 5.8.4 via mfecryptc.dll leads to Database Decryption by Regular Users.17h
CVE-2026-1102143.7 BAJ
38.0%
——11Snowy 3.6.5 contains a hard-coded HMAC key vulnerability that allows unauthenticated attackers to forge download signatures for the /dev/file/download endpoint by using the published FILE_DOWNLOAD_SIGN_SECRET constant. Attackers can compute HMAC-SHA256 signatures of guessed file ids offline to download stored files such as avatars, editor images and attachments.2d
CVE-2026-651988.6 ALT
8.0%
——2Huawei's openUBMC ships a default SNMPv3 USM key that uses one value for both authentication and privacy. An attacker who holds the key (recoverable from the open-source build) can authenticate SNMPv3 to, and decrypt SNMPv3 traffic from, any unit that still carries the shipped key. The build customization `manifest/build/customization/default_password.lua` sets `AuthenticationKey == EncryptionKey == 7df2f29369e3ac3245b2c9d46b67a0ecd055197e41808a34ef325db2f6422581` for the iBMC product build, and the community seed `account/manufacture/default_password.lua` sets both to `7a2f5b86f20233ec7b7bef49643fbf34d86d0cbf6f1f8f5c52d4f30d4536938b`. These are shipped constants, not per-unit values, and they are not rotated by the Administrator password reset, so they survive account provisioning. This is especially dangerous considering that SNMP access is mapped to full device administration privileges, including system reset and firmware upgrades.13h