Share
Lifecycle Timeline
1
Analysis Generated
Jun 18, 2026 - 11:04 vuln.today
DescriptionCVE.org
Alpine Linux: cacti fixed in 1.2.31-0
AnalysisAI
Cacti, the PHP-based network monitoring and graphing solution, has been patched in Alpine Linux at version 1.2.31-0. The nature of the underlying vulnerability is not disclosed in the available intelligence - only the Alpine Linux vendor advisory confirms that a fix was applied at this version boundary. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Access
Patch available
Exploit
upgrade to 1.2.31-0
Impact
vulnerability mitigated
Access
Patch available
Exploit
upgrade to 1.2.31-0
Impact
vulnerability mitigated
Vulnerability AssessmentAI
| Exploitation | Exploitation conditions are unknown - no CVE description, CVSS vector, or CWE is provided. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | Risk assessment is severely constrained by the near-total absence of technical data. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | The attack scenario cannot be determined from available data. No technical description, CVSS vector, or CWE is present to establish attack vector, required privileges, or exploitation method. … |
| Remediation | Upgrade the Cacti package on Alpine Linux to version 1.2.31-0 or later using the Alpine package manager (apk upgrade cacti). … Detailed patch versions, workarounds, and compensating controls in full report. |
Threat intelligence, references, and detailed analysis are available after sign-in.
Same technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today
Destination URL
POC code from unknown sources may be malicious, contain backdoors, or be fake.
Always review and test exploit code in a safe, isolated environment (VM/sandbox).
Verify the source reputation and cross-reference with known databases (Exploit-DB, GitHub Security).