Evidence used
- No CISA KEV confirmation is currently recorded.
- A structured source references public exploit or proof-of-concept material.
- EPSS is 82.29% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2025
CVE-2025-49844High confidence
Redis Lua Use-After-Free may lead to remote code execution
redis · redis
Official source article: GitHub GHSA-4789-QFC9-5F9Q ↗. Check the applicable product and release in the original source.
10.0CriticalCVSS 3.1
Within 72 hours
Patch availableCritical technical impact and a public exploit reference; no CISA KEV confirmation is currently recorded.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityCritical→Operational priority:Critical, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Increase monitoring for the attack path and post-exploitation behaviour described in the report.
Verification
- Confirm that the asset runs redis redis and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Distribution package intelligence
20 package statesRelease-specific package status
Alpine, Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Alpine v3.23v3.23 · community | redict | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 7.3.6-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.23v3.23 · community | redis | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 8.2.2-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.23v3.23 · main | valkey | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 8.1.4-r0 | Alpine Security Database ↗Source updated 3 Oct 2026 |
| Alpine v3.22v3.22 · community | redict | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 7.3.6-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.22v3.22 · community | redis | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 8.0.4-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.22v3.22 · main | valkey | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 8.1.4-r0 | Alpine Security Database ↗Source updated 3 Oct 2026 |
| Alpine v3.21v3.21 · community | redis | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 7.2.11-r0 | Alpine Security Database ↗Source updated 19 Aug 2026 |
| Alpine v3.21v3.21 · main | valkey | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 7.2.11-r0 | Alpine Security Database ↗Source updated 3 Oct 2026 |
| Debian trixietrixie · source | redis | Vendor fix publishedDebian records a fixed source-package version for this release. | 5:8.0.2-3+deb13u1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian trixietrixie · source | valkey | Vendor fix publishedDebian records a fixed source-package version for this release. | 8.1.1+dfsg1-3+deb13u1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian bookwormbookworm · source | redis | Vendor fix publishedDebian records a fixed source-package version for this release. | 5:7.0.15-1~deb12u6 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian forkyforky · source | redict | Vendor fix publishedDebian records a fixed source-package version for this release. | 7.3.6+ds-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian forkyforky · source | redis | Vendor fix publishedDebian records a fixed source-package version for this release. | 5:8.0.4-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian forkyforky · source | valkey | Vendor fix publishedDebian records a fixed source-package version for this release. | 8.1.4+dfsg1-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian sidsid · source | redict | Vendor fix publishedDebian records a fixed source-package version for this release. | 7.3.6+ds-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian sidsid · source | redis | Vendor fix publishedDebian records a fixed source-package version for this release. | 5:8.0.4-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian sidsid · source | valkey | Vendor fix publishedDebian records a fixed source-package version for this release. | 8.1.4+dfsg1-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | lua5.1 | Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | redis | Vendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree. | 5:7.0.15-1ubuntu0.24.04.2 | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | valkey | Vendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree. | 7.2.11+dfsg1-0ubuntu0.2 | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
Direct vendor intelligence
1 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
SEVD-2026-013-01 · CSAF 2.0 · revision 2.0.0 · finalSchneider Electric CPCERTMultiple Third-Party Vulnerabilities on ProLeiT Plant iT/Brewmaxx
The vendor explicitly identifies these products as affected by this CVE.
- ProLeiT Plant iT/Brewmaxx Version 9.60 and above
- Summary
- Additional information about CVE-2025-49844 can be found here: https://www.cve.org/CVERecord?id=CVE-2025-49844
- Remediation
- Patch ProLeiT-2025-001 includes a fix to reduce the risk of exploit: • Install the patch to disable the eval commands in Redis on: o Application Server o VisuHub o Engineering Workstations o Workstation with emergency mode functionality • The patch ProLeiT-2025-001 is available via ProLeiT Support: https://www.proleit.com/support/ • Force usage of secure Redis configuration templates in system settings as documented in the patch manual. • Restart all patched Servers and Workstations
Critical technical impact and a public exploit reference; no CISA KEV confirmation is currently recorded.
Patch available01
What, why and how
Redis is an open source, in-memory database that persists on disk. Versions 8.2.1 and below allow an authenticated user to use a specially crafted Lua script to manipulate the garbage collector, trigger a use-after-free and potentially lead to remote code execution. The problem exists in all versions of Redis with Lua scripting. This issue is fixed in version 8.2.2. To workaround this issue without patching the redis-server executable is to prevent users from executing Lua scripts. This can be done using ACL to restrict EVAL and EVALSHA commands.
What
Redis is an open source, in-memory database that persists on disk. Versions 8.2.1 and below allow an authenticated user to use a specially crafted Lua script to manipulate the garbage collector, trigger a use-after-free and potentially lead to remote code execution. The problem exists in all versions of Redis with Lua scripting. This issue is fixed in version 8.2.2. To workaround this issue without patching the redis-server executable is to prevent users from executing Lua scripts. This can be done using ACL to restrict EVAL and EVALSHA commands.
Why
The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.
How
An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may execute code or commands in the affected security context.
What
Redis is an open source, in-memory database that persists on disk. Versions 8.2.1 and below allow an authenticated user to use a specially crafted Lua script to manipulate the garbage collector, trigger a use-after-free and potentially lead to remote code execution. The problem exists in all versions of Redis with Lua scripting. This issue is fixed in version 8.2.2. To workaround this issue without patching the redis-server executable is to prevent users from executing Lua scripts. This can be done using ACL to restrict EVAL and EVALSHA commands.
Why
The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.
How
An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may execute code or commands in the affected security context.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material Reference recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.CISA Vulnrichment records proof-of-concept exploitation in its SSVC data. BlackTree has not independently executed or validated exploit material.
- Likely attack path
- a network path → Use After Free → execute code or commands in the affected security context
- Attack surface
- Network
- Privileges required
- Low: a basic authenticated account is required
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Changed: exploitation can affect a different security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-416 ↗
CWE-416: Use After Free. The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SChangedScope: The attack can affect a component governed by a different security authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.- Post-exploitation / living off the land
- After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Patch available
- Action
- Patch ProLeiT-2025-001 includes a fix to reduce the risk of exploit: • Install the patch to disable the eval commands in Redis on: o Application Server o VisuHub o Engineering Workstations o Workstation with emergency mode functionality • The patch ProLeiT-2025-001 is available via ProLeiT Support: https://www.proleit.com/support/ • Force usage of secure Redis configuration templates in system settings as documented in the patch manual. • Restart all patched Servers and Workstations
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 3 Oct 2025 · Last source change 20 Mar 2026, 14:08 UTC · CWE-416 · Use After Free
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2025-33178
Product sourceVendor CSAF · Schneider Electric CPCERT
Remediation sourceVendor CSAF · Schneider Electric CPCERT
CWE sourceCNA
NVD statusNVD modified after enrichment
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.