CVE
Ikaros unauthorized tag access and deletion in tag API
Affects Ikaros 1.1.13 and earlier, where authenticated users with tag permissions can reach the tag endpoints. Fixed in 1.2.0.
Written by a model from the sources below. Verify against them.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N
- Exploited
- No known exploitation
- Fix
- Fixed in 1.2.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Authenticated users with tag permissions can reach the tag endpoints. Affects Ikaros up to and including 1.1.13.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 15/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Ikaros, a content management system, has a flaw in its tag API that lets a logged-in user with tag permissions view and delete tags owned by other users. An attacker can do this remotely over the network with a low-privilege account.
Original description
Ikaros is a content management system for ACGMN media. Prior to 1.2.0, server/src/main/java/run/ikaros/server/core/tag/TagEndpoint.java does not enforce tag ownership for authenticated users with tag permissions. GET /tags/condition accepts an arbitrary userId and can enumerate another user's tags, DELETE /tag/id/{id} deletes a tag without comparing its owner to the requester, and DELETE /tag/condition omits userId from its filter and can delete every user's tags matching the supplied condition. This issue is fixed in version 1.2.0.
Who should check
Teams running ikaros-dev Ikaros 1.1.13 or earlier where users hold tag permissions, such as multi-user ACGMN media CMS deployments.
“Any user with tag permissions can enumerate and delete other users' tags”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.2/10CVSS 7.2
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Authenticated users with tag permissions can reach the tag endpoints. Affects Ikaros up to and including 1.1.13.Upgrade to a fixed version: 1.2.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-68918 (Ikaros: Tag API Lacks Ownership Verification), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-68918 (entry last updated 2026-11-17):
Affected:
- ikaros-dev ikaros: fixed in 1.2.0
Fixed versions: 1.2.0.
Conditions (all must be true for the bug to be hit):
- Authenticated users with tag permissions can reach the tag endpoints. (source: https://github.com/ikaros-dev/ikaros/security/advisories/GHSA-rmp3-fcgr-5m83)
- Affects Ikaros up to and including 1.1.13. (source: https://github.com/ikaros-dev/ikaros/security/advisories/GHSA-rmp3-fcgr-5m83)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-68918 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-68918 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/ikaros-dev/ikaros/security/advisories/GHSA-rmp3-fcgr-5m83
- https://github.com/ikaros-dev/ikaros/pull/852
- https://github.com/ikaros-dev/ikaros/commit/875ebdfbacb8bd604996b269511b0d1fe006a99b
- https://github.com/ikaros-dev/ikaros/releases/tag/v1.2.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-68918
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-68918"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- ikaros-dev ikaros
fixed in 1.2.0
Evidence 6
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 3
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-68918
Is CVE-2026-68918 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The tag API does not check that a tag belongs to the user making the request. Users with tag permissions can list other users' tags and delete a tag owned by another user by its ID. The condition-based delete endpoint can also remove matching tags for all users at once.Source: github.com
Which versions are affected by CVE-2026-68918?
ikaros: before 1.2.0.Source: cve.now feed data
Am I affected, and how do I check?
Ikaros up to and including 1.1.13 is affected, in setups where authenticated users hold tag permissions. To check, look up the installed Ikaros version and review which accounts have tag permissions.Source: github.com
How do I fix CVE-2026-68918?
Upgrade Ikaros to 1.2.0 or later, which is the listed fixed version.Source: github.com