Cortex's Alertmanager can expose local files content via specially crafted config

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2022-23536: 0.82% estimated exploitation activity in the next 30 days; percentile 57.19 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact A local file inclusion vulnerability exists in Cortex versions v1.13.0, v1.13.1 and v1.14.0, where a malicious actor could remotely read local files as a result of parsing maliciously crafted Alertmanager configurations when submitted to the Alertmanager Set Configuration API. Only users of the Cortex Alertmanager service using -experimental.alertmanager.enable-api or enableapi: true are affected. Specific Go Packages Affected github.com/cortexproject/cortex/pkg/alertmanager Patches Affected Cortex users are advised to upgrade to versions 1.13.2 or 1.14.1. Workarounds Patching is ultimately advised. Using out-of-bound validation, Cortex administrators may reject Alertmanager configurations containing the apikeyfile setting in the opsgenieconfigs section and opsgenieapikeyfile in the global section before sending to the Set Alertmanager Configuration API as a workaround. References - Fixed Versions: - https://github.com/cortexproject/cortex/releases/tag/v1.14.1 -…

Published by the source

19 Dec 2022, 21:09 UTC

Last modified by the source

2 Oct 2023, 11:04 UTC

Source last checked

26 Oct 2026, 14:59 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-cq2g-pw6q-hf7j

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-23536

Advisory: Cortex's Alertmanager can expose local files content via specially crafted config
IDs: CVE-2022-23536, GHSA-cq2g-pw6q-hf7j
Record: https://patchnext.com/advisories/cve-2022-23536 (revision 1, source checked 26 Oct 2026, 14:59 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/cortexproject/cortex 1.14.1, 1.13.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/cortexproject/cortex: affected >= 1.14.0, <= 1.14.0; >= 1.13.0, < 1.13.2; fixed in 1.13.2, 1.14.1

## Suggested inspection (read-only)
- Go github.com/cortexproject/cortex: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/cortexproject/cortex.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-cq2g-pw6q-hf7j (GitHub-reviewed advisory GHSA-cq2g-pw6q-hf7j lists affected ranges: Go github.com/cortexproject/cortex >=1.14.0 =1.13.0 <1.13.2)

Commands are suggestions: review each one before running it.