Skip to content
Bulwark BlackBulwark Black LLC
Latest
Wasmtime Sandbox Escape: Patch the Engine Behind Your Wasm WorkloadsQuest Quanum Incident: Protect Patient Data While Keeping Orders MovingPulsar Token Bypass: Check Anonymous Fallback and Patch BrokersCisco Expressway Root RCE: Patch the Cluster and Check Service ReachabilityPulsar Manager Is Retired: Remove the Console and Recover Cluster CredentialsArista VCO Exploitation: Patch the Orchestrator, Review Every Portal RoleSafePay Warning: Prove Your Backups Can Survive an Administrator CompromiseTeamUpdraft Compromise: Check Every Connected WordPress Site for PersistenceRailway Secrets Incident: Rotate Credentials, Then Check What They Could ReachLiteLLM 1.107.0 Compromise: Rebuild the Environment, Recover the CredentialsGitLab Regex RCE: Patch the Server, Verify the Delivery ChaineMudhra CA Key Compromise: Check the Trust Stores Beyond Your BrowserPHP2Shell: Patch the Runtime Behind Your WebsitesTrusted Notifications, Untrusted Instructions: Close the Email Content Gap

IOC Passport

CVE-2018-14558

CVEArticle-derived observationCurrent reporting windowReported in 2 articlesWatch this →

A CVE identifier referenced in published reporting. It is vulnerability context, not a malicious indicator or feed verdict.

This value remains inside its 90-day contextual reporting window. Current reporting status is separate from verified-feed admission. Archive-cleared or archived does not mean clean, inactive, benign, remediated, resolved, or safe, and this lifecycle does not change current verified-feed admission.

Current verified-feed status

Checking live guard…

Article reporting and current malicious-feed admission are evaluated separately.

First reported
Last reported
Article count
2
Admission policy
Context only
Research lifecycle
Current

Article reporting history

These dates are report publication dates, not provider sightings or proof of malicious activity.

Malware·Aug 13, 2026

Evooo1Bot Shows Why Exposed Linux and Edge Devices Are Still High-Value Targets

General CTI·Aug 9, 2026

July CVE Data Shows Why Patch Priority Needs Threat Context

Related indicators

Observables that appear alongside this one in the same reporting. Co-occurrence can suggest shared infrastructure, but it does not establish common ownership, campaign identity, or actor attribution.

4c0886349e9d348569fffe1b7a31e474d514508bf0cd6f1e5dd99c2a73525e4d91[.]92[.]40[.]118CVE-2007-3010CVE-2008-4128CVE-2013-3307CVE-2016-20016CVE-2016-6277CVE-2017-17215CVE-2017-5259CVE-2017-7269CVE-2018-0802CVE-2018-11511CVE-2019-14931CVE-2020-10987CVE-2020-22653CVE-2020-22658CVE-2020-25499CVE-2020-36847CVE-2020-8515CVE-2021-24139CVE-2021-27137CVE-2021-29441CVE-2021-3156CVE-2021-31755CVE-2021-32305CVE-2021-36260CVE-2021-4034CVE-2021-46422CVE-2022-26134CVE-2022-29464CVE-2022-30525CVE-2022-35733CVE-2022-37055CVE-2023-1389CVE-2023-25717CVE-2023-34362CVE-2023-4346CVE-2024-10914CVE-2024-29269CVE-2024-42009
Browse all indicators →IOC Archive →Machine-readable feeds →Extract IOCs from text →

Newsletter

The House-Of-L Brief.

Two short reads a day on markets, cyber threats, AI, and geopolitics. A "why it matters" line on every story.

Double opt-in. One-click unsubscribe on every issue. We never share your address.