{"items":[{"id":"NVI-00004275","kind":"vulnerability","title":"Neos Information Disclosure Security Note","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-3c5g-73f7-grvm"],"plain_summary":"OSV carries this publisher advisory for neos/neos, neos/neos, neos/neos, neos/neos, neos/neos. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 3.0.20 for neos/neos. Confirm the publisher’s latest guidance.","source_ids":["sr-5fa106dc998d791626f5ab593d519c24"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 3.1.18 for neos/neos. Confirm the publisher’s latest guidance.","source_ids":["sr-5fa106dc998d791626f5ab593d519c24"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 3.2.14 for neos/neos. Confirm the publisher’s latest guidance.","source_ids":["sr-5fa106dc998d791626f5ab593d519c24"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 3.3.23 for neos/neos. Confirm the publisher’s latest guidance.","source_ids":["sr-5fa106dc998d791626f5ab593d519c24"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 4.0.17 for neos/neos. Confirm the publisher’s latest guidance.","source_ids":["sr-5fa106dc998d791626f5ab593d519c24"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 4.1.16 for neos/neos. Confirm the publisher’s latest guidance.","source_ids":["sr-5fa106dc998d791626f5ab593d519c24"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 4.2.12 for neos/neos. Confirm the publisher’s latest guidance.","source_ids":["sr-5fa106dc998d791626f5ab593d519c24"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 4.3.3 for neos/neos. Confirm the publisher’s latest guidance.","source_ids":["sr-5fa106dc998d791626f5ab593d519c24"],"action_type":"vendor_patch","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-5fa106dc998d791626f5ab593d519c24","url":"https://github.com/advisories/GHSA-3c5g-73f7-grvm","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-3c5g-73f7-grvm","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.654Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-5fa106dc998d791626f5ab593d519c24"],"technology":"neos/neos","known_exclusions":[],"conditions_summary":"Due to reports it has been validated that internal workspaces in Neos are accessible without authentication. Some users assumed this is a planned feature but it is not. A workspace preview should be an additional feature with respective security measures in place.\n\nNote that this only allows reading of internal workspaces not writing. And for clarification, an internal workspace is a workspace that is non public and doesn't have an owner.\n\nGiven that an internal workspace exists in your installation, it is possible to view a page in context of that workspace by opening a link in this format:\n\nhttps://domain/path/to/page.html@workspace-name\n\nThe issue is quite problematic when exploited but at the same time slightly less impactful than it sounds. First of all there is no default internal workspace, so the issue affects only workspaces created by users. That also means the workspace-name, which will also always include a hash is individual to a project and an exploiter must get hold of the workspace-name including the hash. This is non trivial as there is no indication of the existence of it, but obviously brute force and educated guessed can be made.","public_affected_ranges":["ECOSYSTEM: introduced 2.3.0; fixed 3.0.20"]},{"certainty":"source_listed","source_ids":["sr-5fa106dc998d791626f5ab593d519c24"],"technology":"neos/neos","known_exclusions":[],"conditions_summary":"Due to reports it has been validated that internal workspaces in Neos are accessible without authentication. Some users assumed this is a planned feature but it is not. A workspace preview should be an additional feature with respective security measures in place.\n\nNote that this only allows reading of internal workspaces not writing. And for clarification, an internal workspace is a workspace that is non public and doesn't have an owner.\n\nGiven that an internal workspace exists in your installation, it is possible to view a page in context of that workspace by opening a link in this format:\n\nhttps://domain/path/to/page.html@workspace-name\n\nThe issue is quite problematic when exploited but at the same time slightly less impactful than it sounds. First of all there is no default internal workspace, so the issue affects only workspaces created by users. That also means the workspace-name, which will also always include a hash is individual to a project and an exploiter must get hold of the workspace-name including the hash. This is non trivial as there is no indication of the existence of it, but obviously brute force and educated guessed can be made.","public_affected_ranges":["ECOSYSTEM: introduced 3.1.0; fixed 3.1.18"]},{"certainty":"source_listed","source_ids":["sr-5fa106dc998d791626f5ab593d519c24"],"technology":"neos/neos","known_exclusions":[],"conditions_summary":"Due to reports it has been validated that internal workspaces in Neos are accessible without authentication. Some users assumed this is a planned feature but it is not. A workspace preview should be an additional feature with respective security measures in place.\n\nNote that this only allows reading of internal workspaces not writing. And for clarification, an internal workspace is a workspace that is non public and doesn't have an owner.\n\nGiven that an internal workspace exists in your installation, it is possible to view a page in context of that workspace by opening a link in this format:\n\nhttps://domain/path/to/page.html@workspace-name\n\nThe issue is quite problematic when exploited but at the same time slightly less impactful than it sounds. First of all there is no default internal workspace, so the issue affects only workspaces created by users. That also means the workspace-name, which will also always include a hash is individual to a project and an exploiter must get hold of the workspace-name including the hash. This is non trivial as there is no indication of the existence of it, but obviously brute force and educated guessed can be made.","public_affected_ranges":["ECOSYSTEM: introduced 3.2.0; fixed 3.2.14"]},{"certainty":"source_listed","source_ids":["sr-5fa106dc998d791626f5ab593d519c24"],"technology":"neos/neos","known_exclusions":[],"conditions_summary":"Due to reports it has been validated that internal workspaces in Neos are accessible without authentication. Some users assumed this is a planned feature but it is not. A workspace preview should be an additional feature with respective security measures in place.\n\nNote that this only allows reading of internal workspaces not writing. And for clarification, an internal workspace is a workspace that is non public and doesn't have an owner.\n\nGiven that an internal workspace exists in your installation, it is possible to view a page in context of that workspace by opening a link in this format:\n\nhttps://domain/path/to/page.html@workspace-name\n\nThe issue is quite problematic when exploited but at the same time slightly less impactful than it sounds. First of all there is no default internal workspace, so the issue affects only workspaces created by users. That also means the workspace-name, which will also always include a hash is individual to a project and an exploiter must get hold of the workspace-name including the hash. This is non trivial as there is no indication of the existence of it, but obviously brute force and educated guessed can be made.","public_affected_ranges":["ECOSYSTEM: introduced 3.3.0; fixed 3.3.23"]},{"certainty":"source_listed","source_ids":["sr-5fa106dc998d791626f5ab593d519c24"],"technology":"neos/neos","known_exclusions":[],"conditions_summary":"Due to reports it has been validated that internal workspaces in Neos are accessible without authentication. Some users assumed this is a planned feature but it is not. A workspace preview should be an additional feature with respective security measures in place.\n\nNote that this only allows reading of internal workspaces not writing. And for clarification, an internal workspace is a workspace that is non public and doesn't have an owner.\n\nGiven that an internal workspace exists in your installation, it is possible to view a page in context of that workspace by opening a link in this format:\n\nhttps://domain/path/to/page.html@workspace-name\n\nThe issue is quite problematic when exploited but at the same time slightly less impactful than it sounds. First of all there is no default internal workspace, so the issue affects only workspaces created by users. That also means the workspace-name, which will also always include a hash is individual to a project and an exploiter must get hold of the workspace-name including the hash. This is non trivial as there is no indication of the existence of it, but obviously brute force and educated guessed can be made.","public_affected_ranges":["ECOSYSTEM: introduced 4.0.0; fixed 4.0.17"]},{"certainty":"source_listed","source_ids":["sr-5fa106dc998d791626f5ab593d519c24"],"technology":"neos/neos","known_exclusions":[],"conditions_summary":"Due to reports it has been validated that internal workspaces in Neos are accessible without authentication. Some users assumed this is a planned feature but it is not. A workspace preview should be an additional feature with respective security measures in place.\n\nNote that this only allows reading of internal workspaces not writing. And for clarification, an internal workspace is a workspace that is non public and doesn't have an owner.\n\nGiven that an internal workspace exists in your installation, it is possible to view a page in context of that workspace by opening a link in this format:\n\nhttps://domain/path/to/page.html@workspace-name\n\nThe issue is quite problematic when exploited but at the same time slightly less impactful than it sounds. First of all there is no default internal workspace, so the issue affects only workspaces created by users. That also means the workspace-name, which will also always include a hash is individual to a project and an exploiter must get hold of the workspace-name including the hash. This is non trivial as there is no indication of the existence of it, but obviously brute force and educated guessed can be made.","public_affected_ranges":["ECOSYSTEM: introduced 4.1.0; fixed 4.1.16"]},{"certainty":"source_listed","source_ids":["sr-5fa106dc998d791626f5ab593d519c24"],"technology":"neos/neos","known_exclusions":[],"conditions_summary":"Due to reports it has been validated that internal workspaces in Neos are accessible without authentication. Some users assumed this is a planned feature but it is not. A workspace preview should be an additional feature with respective security measures in place.\n\nNote that this only allows reading of internal workspaces not writing. And for clarification, an internal workspace is a workspace that is non public and doesn't have an owner.\n\nGiven that an internal workspace exists in your installation, it is possible to view a page in context of that workspace by opening a link in this format:\n\nhttps://domain/path/to/page.html@workspace-name\n\nThe issue is quite problematic when exploited but at the same time slightly less impactful than it sounds. First of all there is no default internal workspace, so the issue affects only workspaces created by users. That also means the workspace-name, which will also always include a hash is individual to a project and an exploiter must get hold of the workspace-name including the hash. This is non trivial as there is no indication of the existence of it, but obviously brute force and educated guessed can be made.","public_affected_ranges":["ECOSYSTEM: introduced 4.2.0; fixed 4.2.12"]},{"certainty":"source_listed","source_ids":["sr-5fa106dc998d791626f5ab593d519c24"],"technology":"neos/neos","known_exclusions":[],"conditions_summary":"Due to reports it has been validated that internal workspaces in Neos are accessible without authentication. Some users assumed this is a planned feature but it is not. A workspace preview should be an additional feature with respective security measures in place.\n\nNote that this only allows reading of internal workspaces not writing. And for clarification, an internal workspace is a workspace that is non public and doesn't have an owner.\n\nGiven that an internal workspace exists in your installation, it is possible to view a page in context of that workspace by opening a link in this format:\n\nhttps://domain/path/to/page.html@workspace-name\n\nThe issue is quite problematic when exploited but at the same time slightly less impactful than it sounds. First of all there is no default internal workspace, so the issue affects only workspaces created by users. That also means the workspace-name, which will also always include a hash is individual to a project and an exploiter must get hold of the workspace-name including the hash. This is non trivial as there is no indication of the existence of it, but obviously brute force and educated guessed can be made.","public_affected_ranges":["ECOSYSTEM: introduced 4.3.0; fixed 4.3.3"]}],"null_published_at":"2026-10-31T22:12:52.638Z","source_updated_at":"2024-12-02T05:49:32.920Z","source_disclosed_at":"2024-05-17T22:54:47.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-31T21:41:49.654Z"}],"next_cursor":null,"snapshot_revision":"42594"}