{"items":[{"id":"NVI-00011996","kind":"vulnerability","title":"Vikunja: Any user can enumerate every team and its members by attaching arbitrary teams to a throwaway project","revision":4,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-39p5-2wrr-xh29","CVE-2026-91980"],"plain_summary":"GitHub lists this reviewed advisory for code.vikunja.io/api. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-2cab09e369bb76a712db24a594c7aee9"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-09-16T19:49:18.987Z","value":"4.3 MEDIUM (3.1)","meaning":"disclosure@vulncheck.com severity; no combined Null risk score.","source_id":"sr-6ce1eb9b8191c8c14caf60b3e29423da"},{"kind":"CVSS","as_of":"2026-09-16T19:49:18.987Z","value":"5.3 MEDIUM (4.0)","meaning":"disclosure@vulncheck.com severity; no combined Null risk score.","source_id":"sr-6ce1eb9b8191c8c14caf60b3e29423da"},{"kind":"EPSS","as_of":"2026-11-01T12:00:16.000Z","value":"0.306%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.23445. Missing scores are unknown.","source_id":"sr-2cab09e369bb76a712db24a594c7aee9"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-7e52e49dbf28e6126fe999bb5d1a09ce","url":"https://github.com/advisories/GHSA-39p5-2wrr-xh29","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-39p5-2wrr-xh29","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T23:14:22.124Z"},{"id":"sr-6ce1eb9b8191c8c14caf60b3e29423da","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-91980","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-91980","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-04T09:59:50.242Z"},{"id":"sr-2cab09e369bb76a712db24a594c7aee9","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-91980","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:29:11.296Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-7e52e49dbf28e6126fe999bb5d1a09ce"],"technology":"code.vikunja.io/api","known_exclusions":[],"conditions_summary":"### Summary\nWhen you share a project with a team, the API lets you attach any team on the instance, including teams you have nothing to do with, as long as you're an admin of the project. Listing a project's teams then returns each team's full member roster. So any logged-in user can spin up a throwaway project, attach team IDs one by one, and read back the name, description, and complete member list of every team on the instance. Normally you can only see teams you belong to; this path ignores that.\n\n### Details\nSharing a project with a team is a two-step flow: you PUT a team to the project, then you GET the project's teams to see them. The share endpoint only enforces that you're an admin of the target project, it doesn't care whether the team you're referencing is one you're allowed to see. Any existing team ID is accepted.\n\nThe listing endpoint is even more permissive: read access to the project is enough, which you obviously have on a project you created. And its response isn't just a list of team names, it includes each team's description, creator, and a full members array with every member's username, display name, and admin flag.\n\nPut together, an attacker who owns a single","public_affected_ranges":["<= 2.5.0"]}],"null_published_at":"2026-11-07T07:07:42.487Z","source_updated_at":"2026-10-09T20:52:28.000Z","source_disclosed_at":"2026-10-09T20:52:27.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T23:14:22.124Z"},{"id":"NVI-00011996","kind":"vulnerability","title":"Vikunja: Any user can enumerate every team and its members by attaching arbitrary teams to a throwaway project","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-39p5-2wrr-xh29","CVE-2026-91980"],"plain_summary":"GitHub lists this reviewed advisory for code.vikunja.io/api. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-2cab09e369bb76a712db24a594c7aee9"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"EPSS","as_of":"2026-11-01T12:00:16.000Z","value":"0.306%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.23445. Missing scores are unknown.","source_id":"sr-2cab09e369bb76a712db24a594c7aee9"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-7e52e49dbf28e6126fe999bb5d1a09ce","url":"https://github.com/advisories/GHSA-39p5-2wrr-xh29","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-39p5-2wrr-xh29","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T23:14:22.124Z"},{"id":"sr-2cab09e369bb76a712db24a594c7aee9","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-91980","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:29:11.296Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-7e52e49dbf28e6126fe999bb5d1a09ce"],"technology":"code.vikunja.io/api","known_exclusions":[],"conditions_summary":"### Summary\nWhen you share a project with a team, the API lets you attach any team on the instance, including teams you have nothing to do with, as long as you're an admin of the project. Listing a project's teams then returns each team's full member roster. So any logged-in user can spin up a throwaway project, attach team IDs one by one, and read back the name, description, and complete member list of every team on the instance. Normally you can only see teams you belong to; this path ignores that.\n\n### Details\nSharing a project with a team is a two-step flow: you PUT a team to the project, then you GET the project's teams to see them. The share endpoint only enforces that you're an admin of the target project, it doesn't care whether the team you're referencing is one you're allowed to see. Any existing team ID is accepted.\n\nThe listing endpoint is even more permissive: read access to the project is enough, which you obviously have on a project you created. And its response isn't just a list of team names, it includes each team's description, creator, and a full members array with every member's username, display name, and admin flag.\n\nPut together, an attacker who owns a single","public_affected_ranges":["<= 2.5.0"]}],"null_published_at":"2026-11-06T15:18:11.461Z","source_updated_at":"2026-10-09T20:52:28.000Z","source_disclosed_at":"2026-10-09T20:52:27.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T23:14:22.124Z"},{"id":"NVI-00011996","kind":"vulnerability","title":"Vikunja: Any user can enumerate every team and its members by attaching arbitrary teams to a throwaway project","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-39p5-2wrr-xh29","CVE-2026-91980"],"plain_summary":"GitHub lists this reviewed advisory for code.vikunja.io/api. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-16aba609a4958d924006371b23244085"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.306%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.23451. Missing scores are unknown.","source_id":"sr-16aba609a4958d924006371b23244085"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-7e52e49dbf28e6126fe999bb5d1a09ce","url":"https://github.com/advisories/GHSA-39p5-2wrr-xh29","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-39p5-2wrr-xh29","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T23:14:22.124Z"},{"id":"sr-16aba609a4958d924006371b23244085","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-91980","publisher":"FIRST EPSS","observed_at":"2026-11-01T01:39:43.089Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-7e52e49dbf28e6126fe999bb5d1a09ce"],"technology":"code.vikunja.io/api","known_exclusions":[],"conditions_summary":"### Summary\nWhen you share a project with a team, the API lets you attach any team on the instance, including teams you have nothing to do with, as long as you're an admin of the project. Listing a project's teams then returns each team's full member roster. So any logged-in user can spin up a throwaway project, attach team IDs one by one, and read back the name, description, and complete member list of every team on the instance. Normally you can only see teams you belong to; this path ignores that.\n\n### Details\nSharing a project with a team is a two-step flow: you PUT a team to the project, then you GET the project's teams to see them. The share endpoint only enforces that you're an admin of the target project, it doesn't care whether the team you're referencing is one you're allowed to see. Any existing team ID is accepted.\n\nThe listing endpoint is even more permissive: read access to the project is enough, which you obviously have on a project you created. And its response isn't just a list of team names, it includes each team's description, creator, and a full members array with every member's username, display name, and admin flag.\n\nPut together, an attacker who owns a single","public_affected_ranges":["<= 2.5.0"]}],"null_published_at":"2026-11-01T14:34:14.100Z","source_updated_at":"2026-10-09T20:52:28.000Z","source_disclosed_at":"2026-10-09T20:52:27.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T23:14:22.124Z"},{"id":"NVI-00011996","kind":"vulnerability","title":"Vikunja: Any user can enumerate every team and its members by attaching arbitrary teams to a throwaway project","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-39p5-2wrr-xh29","CVE-2026-91980"],"plain_summary":"GitHub lists this reviewed advisory for code.vikunja.io/api. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-7e52e49dbf28e6126fe999bb5d1a09ce"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-7e52e49dbf28e6126fe999bb5d1a09ce","url":"https://github.com/advisories/GHSA-39p5-2wrr-xh29","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-39p5-2wrr-xh29","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T23:14:22.124Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-7e52e49dbf28e6126fe999bb5d1a09ce"],"technology":"code.vikunja.io/api","known_exclusions":[],"conditions_summary":"### Summary\nWhen you share a project with a team, the API lets you attach any team on the instance, including teams you have nothing to do with, as long as you're an admin of the project. Listing a project's teams then returns each team's full member roster. So any logged-in user can spin up a throwaway project, attach team IDs one by one, and read back the name, description, and complete member list of every team on the instance. Normally you can only see teams you belong to; this path ignores that.\n\n### Details\nSharing a project with a team is a two-step flow: you PUT a team to the project, then you GET the project's teams to see them. The share endpoint only enforces that you're an admin of the target project, it doesn't care whether the team you're referencing is one you're allowed to see. Any existing team ID is accepted.\n\nThe listing endpoint is even more permissive: read access to the project is enough, which you obviously have on a project you created. And its response isn't just a list of team names, it includes each team's description, creator, and a full members array with every member's username, display name, and admin flag.\n\nPut together, an attacker who owns a single","public_affected_ranges":["<= 2.5.0"]}],"null_published_at":"2026-11-01T01:03:56.620Z","source_updated_at":"2026-10-09T20:52:28.000Z","source_disclosed_at":"2026-10-09T20:52:27.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T23:14:22.124Z"}],"next_cursor":null,"snapshot_revision":"42594"}