Security readout for executives and security teams
Plain-English summary
CVE-2026-22799 affects emlog 2.6.1 and earlier. A media upload REST API can accept unsafe files, including PHP scripts. If an attacker can use a valid API key or admin session, they may upload code that runs on the web server, potentially causing full server compromise.
Executive priority
Treat this as urgent for any exposed emlog deployment. The business risk is server takeover if an attacker can reach the upload API with valid credentials or keys. Prioritize inventory, vendor remediation review, and containment of upload execution paths.
Technical view
The issue is CWE-434 unrestricted upload in /index.php?rest-api=upload. Sources state file type, extension, and content validation are insufficient. Uploaded PHP can be executed for remote code execution. The CVSS 4.0 score is 9.3 critical, though the description indicates practical access may require an API key or admin session cookie.
Likely exposure
Internet-facing emlog sites running version 2.6.1 or earlier are the main concern, especially where the REST API upload feature is enabled or API keys may be exposed. Exposure depends on configuration and credential/API-key access.
Exploitation context
The provided sources do not show CISA KEV listing or confirmed active exploitation. Exploitation requires the ability to access the upload API using a valid API key or admin session, or to obtain an API key through another application weakness.
Researcher notes
There is a notable access-model ambiguity: CVSS lists PR:N, while the description says a valid API key or admin session is needed. Do not assume unauthenticated exploitation without confirming the advisory details. The referenced commit likely contains the vendor change, but fixed release details are not provided in the bundle.
Mitigation direction
- Identify any emlog deployments and confirm their versions.
- Review the GitHub advisory and commit for vendor-provided remediation details.
- Upgrade or patch according to official emlog guidance when available.
- Disable or restrict REST API media uploads if not required.
- Rotate API keys and invalidate suspicious admin sessions.
- Restrict web server execution in upload directories where feasible.
Validation and detection
- Inventory public and internal emlog instances.
- Confirm whether each instance runs version 2.6.1 or earlier.
- Check whether the REST API upload endpoint is enabled or reachable.
- Review admin accounts, API key exposure, and recent configuration changes.
- Inspect upload directories for unexpected executable files.
- Review web and application logs for suspicious upload activity.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-434: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-22799 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.3 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/emlog/emlog/security/advisories/GHSA-p837-mrw9-5x5jCVE reference · x_refsource_CONFIRM
- https://github.com/emlog/emlog/commit/429b02fda842254b9b9b39303e9161999c180560CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.