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 open-source network graphing and monitoring solution, received a security fix in Alpine Linux package version 1.2.31-0. The nature, impact class, and root cause of this vulnerability are not disclosed in the available intelligence data - the sole data point is the Alpine Linux vendor advisory confirming a patched package. …
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
Unknown access method
Exploit
Unknown exploitation technique
Impact
Unknown impact
Access
Unknown access method
Exploit
Unknown exploitation technique
Impact
Unknown impact
Vulnerability AssessmentAI
| Exploitation | Exploitation conditions cannot be determined - no CVSS vector, no CWE, and no vulnerability description beyond the patch notice were provided. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | Risk assessment is severely constrained by absent data. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | No exploit scenario can be responsibly constructed from the available data. The vulnerability type, attack vector, and required conditions are all undisclosed. … |
| Remediation | Vendor-released patch: Alpine Linux package cacti 1.2.31-0. … 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).