CVE-2026-26978

{"id": "CVE-2026-26978", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-26978", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "total"}], "version": "2.0.3", "timestamp": "2026-05-19T00:00:00+00:00"}}], "cvssMetricV40": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 8.6, "Automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "HIGH", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/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", "exploitMaturity": "NOT_DEFINED", "providerUrgency": "NOT_DEFINED", "userInteraction": "NONE", "attackComplexity": "LOW", "attackRequirements": "NONE", "privilegesRequired": "LOW", "subIntegrityImpact": "NONE", "vulnIntegrityImpact": "HIGH", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "NONE", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "NONE", "vulnConfidentialityImpact": "HIGH", "confidentialityRequirement": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED"}}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "FreePBX", "product": "security-reporting", "versions": [{"status": "affected", "version": "< 16.0.71"}, {"status": "affected", "version": ">= 17.0.0, < 17.0.6"}]}]}], "published": "2026-05-18T21:16:39.723", "references": [{"url": "https://github.com/FreePBX/backup/commit/45c57e1207cbf9fd1c5f76f8a3e72d204a69a472", "source": "security-advisories@github.com"}, {"url": "https://github.com/FreePBX/backup/commit/64781af5c80cce0cff21a981be4d8e6a7a71f2c4", "source": "security-advisories@github.com"}, {"url": "https://github.com/FreePBX/security-reporting/security/advisories/GHSA-5v7h-49gr-jcwr", "source": "security-advisories@github.com"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-502"}]}], "descriptions": [{"lang": "en", "value": "FreePBX is an open source IP PBX. In versions below 16.0.71 and 17.0.6, the backup module does not properly sanitize data during restore operations, potentially leading to compromise if the backup contains carefully crafted hostile data. During backup restore operations, FreePBX extracts selected files from a user-supplied tar archive. If a malicious file exists in the archive, it is read and passed directly to unserialize() without validation, class restrictions, or integrity checks. This issue allows Remote Code Execution during restoration of the backup as the web server user (typically asterisk or www-data). The attack does not require shell access, CLI access, or filesystem write permissions beyond the normal restore workflow. Authentication with a known username that has sufficient access permissions and/or write access to backup files is required. This issue has been fixed in versions 16.0.71 and 17.0.6."}, {"lang": "es", "value": "FreePBX es una PBX IP de c\u00f3digo abierto. En versiones anteriores a la 16.0.71 y 17.0.6, el m\u00f3dulo de copia de seguridad no sanea correctamente los datos durante las operaciones de restauraci\u00f3n, lo que podr\u00eda llevar a un compromiso si la copia de seguridad contiene datos hostiles cuidadosamente elaborados. Durante las operaciones de restauraci\u00f3n de la copia de seguridad, FreePBX extrae archivos seleccionados de un archivo tar proporcionado por el usuario. Si existe un archivo malicioso en el archivo, se lee y se pasa directamente a unserialize() sin validaci\u00f3n, restricciones de clase o comprobaciones de integridad. Este problema permite la Ejecuci\u00f3n Remota de C\u00f3digo durante la restauraci\u00f3n de la copia de seguridad como el usuario del servidor web (t\u00edpicamente asterisk o www-data). El ataque no requiere acceso a shell, acceso CLI o permisos de escritura en el sistema de archivos m\u00e1s all\u00e1 del flujo de trabajo de restauraci\u00f3n normal. Se requiere Autenticaci\u00f3n con un nombre de usuario conocido que tenga permisos de acceso suficientes y/o acceso de escritura a los archivos de copia de seguridad. Este problema ha sido solucionado en las versiones 16.0.71 y 17.0.6."}], "lastModified": "2026-07-24T13:10:00.223", "sourceIdentifier": "security-advisories@github.com"}