{"api_version":"1","generated_at":"2026-08-20T13:52:44+00:00","cve":"CVE-2026-23933","urls":{"html":"https://cve.report/CVE-2026-23933","api":"https://cve.report/api/cve/CVE-2026-23933.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-23933","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-23933"},"summary":{"title":"Hardcoded session key in Zabbix 7.4","description":"In Zabbix 7.4 the cryptographic key used for signing Frontend sessions has been erroneously written to the database seed. Currently the only known exploitation scenario is for deployments that utilize both - SAML authentication and guest users. In such cases the key can be used to forge valid session cookies, potentially leading to unauthorized access. For other Zabbix deployments this does not have a known impact.","state":"PUBLISHED","assigner":"Zabbix","published_at":"2026-08-18 13:17:21","updated_at":"2026-08-19 04:16:58"},"problem_types":["CWE-259","CWE-259 CWE-259 CWE-259: Use of Hard-coded Password"],"metrics":[{"version":"4.0","source":"security@zabbix.com","type":"Secondary","score":"7.7","severity":"HIGH","vector":"CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","data":{"version":"4.0","vectorString":"CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","baseScore":7.7,"baseSeverity":"HIGH","attackVector":"ADJACENT","attackComplexity":"LOW","attackRequirements":"PRESENT","privilegesRequired":"NONE","userInteraction":"NONE","vulnConfidentialityImpact":"HIGH","vulnIntegrityImpact":"HIGH","vulnAvailabilityImpact":"HIGH","subConfidentialityImpact":"NONE","subIntegrityImpact":"NONE","subAvailabilityImpact":"NONE","exploitMaturity":"NOT_DEFINED","confidentialityRequirement":"NOT_DEFINED","integrityRequirement":"NOT_DEFINED","availabilityRequirement":"NOT_DEFINED","modifiedAttackVector":"NOT_DEFINED","modifiedAttackComplexity":"NOT_DEFINED","modifiedAttackRequirements":"NOT_DEFINED","modifiedPrivilegesRequired":"NOT_DEFINED","modifiedUserInteraction":"NOT_DEFINED","modifiedVulnConfidentialityImpact":"NOT_DEFINED","modifiedVulnIntegrityImpact":"NOT_DEFINED","modifiedVulnAvailabilityImpact":"NOT_DEFINED","modifiedSubConfidentialityImpact":"NOT_DEFINED","modifiedSubIntegrityImpact":"NOT_DEFINED","modifiedSubAvailabilityImpact":"NOT_DEFINED","Safety":"NOT_DEFINED","Automatable":"NOT_DEFINED","Recovery":"NOT_DEFINED","valueDensity":"NOT_DEFINED","vulnerabilityResponseEffort":"NOT_DEFINED","providerUrgency":"NOT_DEFINED"}},{"version":"4.0","source":"CNA","type":"CVSS","score":"7.7","severity":"HIGH","vector":"CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","data":{"Automatable":"NOT_DEFINED","Recovery":"NOT_DEFINED","Safety":"NOT_DEFINED","attackComplexity":"LOW","attackRequirements":"PRESENT","attackVector":"ADJACENT","baseScore":7.7,"baseSeverity":"HIGH","exploitMaturity":"NOT_DEFINED","privilegesRequired":"NONE","providerUrgency":"NOT_DEFINED","subAvailabilityImpact":"NONE","subConfidentialityImpact":"NONE","subIntegrityImpact":"NONE","userInteraction":"NONE","valueDensity":"NOT_DEFINED","vectorString":"CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0","vulnAvailabilityImpact":"HIGH","vulnConfidentialityImpact":"HIGH","vulnIntegrityImpact":"HIGH","vulnerabilityResponseEffort":"NOT_DEFINED"}}],"references":[{"url":"https://support.zabbix.com/browse/ZBX-28071","name":"https://support.zabbix.com/browse/ZBX-28071","refsource":"security@zabbix.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-23933","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23933","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Zabbix","product":"Zabbix","version":"affected 7.4.0 7.4.10 git","platforms":[]}],"timeline":[],"solutions":[{"source":"CNA","title":"","value":"Upgrade Zabbix Server to the latest version, an upgrade patch will remove the session key from the DB.","time":"","lang":"en"}],"workarounds":[{"source":"CNA","title":"","value":"As a workaround, the pre-seeded session key can be manually cleared from Zabbix DB by setting value of 'settings.session_key' to an empty string. Zabbix Frontend will then generate a new random key.","time":"","lang":"en"}],"exploits":[],"credits":[{"source":"CNA","value":"Zabbix wants to thank Daniel Shemesh and Or Ida for submitting this report on the HackerOne bug bounty platform.","lang":"en"}],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"23933","cve":"CVE-2026-23933","epss":"0.001990000","percentile":"0.100680000","score_date":"2026-08-19","updated_at":"2026-08-20 00:13:10"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"adp":[{"metrics":[{"other":{"content":{"id":"CVE-2026-23933","options":[{"Exploitation":"none"},{"Automatable":"no"},{"Technical Impact":"total"}],"role":"CISA Coordinator","timestamp":"2026-08-18T00:00:00+00:00","version":"2.0.3"},"type":"ssvc"}}],"providerMetadata":{"dateUpdated":"2026-08-19T03:55:57.404Z","orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","shortName":"CISA-ADP"},"title":"CISA ADP Vulnrichment"}],"cna":{"affected":[{"defaultStatus":"unknown","modules":["Frontend","Server"],"product":"Zabbix","repo":"https://git.zabbix.com/","vendor":"Zabbix","versions":[{"changes":[{"at":"7.4.11","status":"unaffected"}],"lessThanOrEqual":"7.4.10","status":"affected","version":"7.4.0","versionType":"git"}]}],"configurations":[{"lang":"en","supportingMedia":[{"base64":false,"type":"text/html","value":"<p>An unauthenticated attacker with Frontend access might be able to generate valid session cookies in certain deployments.</p>"}],"value":"An unauthenticated attacker with Frontend access might be able to generate valid session cookies in certain deployments."}],"credits":[{"lang":"en","type":"reporter","value":"Zabbix wants to thank Daniel Shemesh and Or Ida for submitting this report on the HackerOne bug bounty platform."}],"descriptions":[{"lang":"en","supportingMedia":[{"base64":false,"type":"text/html","value":"<p>In Zabbix 7.4 the cryptographic key used for signing Frontend sessions has been erroneously written to the database seed. Currently the only known exploitation scenario is for deployments that utilize both - SAML authentication and guest users. In such cases the key can be used to forge valid session cookies, potentially leading to unauthorized access. For other Zabbix deployments this does not have a known impact.</p>"}],"value":"In Zabbix 7.4 the cryptographic key used for signing Frontend sessions has been erroneously written to the database seed. Currently the only known exploitation scenario is for deployments that utilize both - SAML authentication and guest users. In such cases the key can be used to forge valid session cookies, potentially leading to unauthorized access. For other Zabbix deployments this does not have a known impact."}],"impacts":[{"capecId":"CAPEC-560","descriptions":[{"lang":"en","value":"CAPEC-560: Use of Known Domain Credentials"}]}],"metrics":[{"cvssV4_0":{"Automatable":"NOT_DEFINED","Recovery":"NOT_DEFINED","Safety":"NOT_DEFINED","attackComplexity":"LOW","attackRequirements":"PRESENT","attackVector":"ADJACENT","baseScore":7.7,"baseSeverity":"HIGH","exploitMaturity":"NOT_DEFINED","privilegesRequired":"NONE","providerUrgency":"NOT_DEFINED","subAvailabilityImpact":"NONE","subConfidentialityImpact":"NONE","subIntegrityImpact":"NONE","userInteraction":"NONE","valueDensity":"NOT_DEFINED","vectorString":"CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0","vulnAvailabilityImpact":"HIGH","vulnConfidentialityImpact":"HIGH","vulnIntegrityImpact":"HIGH","vulnerabilityResponseEffort":"NOT_DEFINED"},"format":"CVSS","scenarios":[{"lang":"en","value":"GENERAL"}]}],"problemTypes":[{"descriptions":[{"cweId":"CWE-259","description":"CWE-259 CWE-259: Use of Hard-coded Password","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-08-18T12:18:09.643Z","orgId":"72de3e22-0555-4a0d-ae81-9249e0f0a1e8","shortName":"Zabbix"},"references":[{"url":"https://support.zabbix.com/browse/ZBX-28071"}],"solutions":[{"lang":"en","supportingMedia":[{"base64":false,"type":"text/html","value":"<p>Upgrade Zabbix Server to the latest version, an upgrade patch will remove the session key from the DB.</p>"}],"value":"Upgrade Zabbix Server to the latest version, an upgrade patch will remove the session key from the DB."}],"source":{"discovery":"EXTERNAL"},"title":"Hardcoded session key in Zabbix 7.4","workarounds":[{"lang":"en","supportingMedia":[{"base64":false,"type":"text/html","value":"<p>As a workaround, the pre-seeded session key can be manually cleared from Zabbix DB by setting value of 'settings.session_key' to an empty string. Zabbix Frontend will then generate a new random key.</p>"}],"value":"As a workaround, the pre-seeded session key can be manually cleared from Zabbix DB by setting value of 'settings.session_key' to an empty string. Zabbix Frontend will then generate a new random key."}],"x_generator":{"engine":"Vulnogram 1.0.4"}}},"cveMetadata":{"assignerOrgId":"72de3e22-0555-4a0d-ae81-9249e0f0a1e8","assignerShortName":"Zabbix","cveId":"CVE-2026-23933","datePublished":"2026-08-18T12:18:09.643Z","dateReserved":"2026-01-19T14:03:13.686Z","dateUpdated":"2026-08-19T03:55:57.404Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-08-18 13:17:21","lastModifiedDate":"2026-08-19 04:16:58","problem_types":["CWE-259","CWE-259 CWE-259 CWE-259: Use of Hard-coded Password"],"metrics":{"cvssMetricV40":[{"source":"security@zabbix.com","type":"Secondary","cvssData":{"version":"4.0","vectorString":"CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","baseScore":7.7,"baseSeverity":"HIGH","attackVector":"ADJACENT","attackComplexity":"LOW","attackRequirements":"PRESENT","privilegesRequired":"NONE","userInteraction":"NONE","vulnConfidentialityImpact":"HIGH","vulnIntegrityImpact":"HIGH","vulnAvailabilityImpact":"HIGH","subConfidentialityImpact":"NONE","subIntegrityImpact":"NONE","subAvailabilityImpact":"NONE","exploitMaturity":"NOT_DEFINED","confidentialityRequirement":"NOT_DEFINED","integrityRequirement":"NOT_DEFINED","availabilityRequirement":"NOT_DEFINED","modifiedAttackVector":"NOT_DEFINED","modifiedAttackComplexity":"NOT_DEFINED","modifiedAttackRequirements":"NOT_DEFINED","modifiedPrivilegesRequired":"NOT_DEFINED","modifiedUserInteraction":"NOT_DEFINED","modifiedVulnConfidentialityImpact":"NOT_DEFINED","modifiedVulnIntegrityImpact":"NOT_DEFINED","modifiedVulnAvailabilityImpact":"NOT_DEFINED","modifiedSubConfidentialityImpact":"NOT_DEFINED","modifiedSubIntegrityImpact":"NOT_DEFINED","modifiedSubAvailabilityImpact":"NOT_DEFINED","Safety":"NOT_DEFINED","Automatable":"NOT_DEFINED","Recovery":"NOT_DEFINED","valueDensity":"NOT_DEFINED","vulnerabilityResponseEffort":"NOT_DEFINED","providerUrgency":"NOT_DEFINED"}}],"ssvcV203":[{"source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","ssvcData":{"timestamp":"2026-08-18T00:00:00+00:00","id":"CVE-2026-23933","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"total"}],"role":"CISA Coordinator","version":"2.0.3"}}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"23933","Ordinal":"1","Title":"Hardcoded session key in Zabbix 7.4","CVE":"CVE-2026-23933","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"23933","Ordinal":"1","NoteData":"In Zabbix 7.4 the cryptographic key used for signing Frontend sessions has been erroneously written to the database seed. Currently the only known exploitation scenario is for deployments that utilize both - SAML authentication and guest users. In such cases the key can be used to forge valid session cookies, potentially leading to unauthorized access. For other Zabbix deployments this does not have a known impact.","Type":"Description","Title":"Hardcoded session key in Zabbix 7.4"}]}}}